Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Front-end handling of optional new and const. #30922

Closed
lrhn opened this issue Sep 28, 2017 · 8 comments
Closed

Front-end handling of optional new and const. #30922

lrhn opened this issue Sep 28, 2017 · 8 comments
Assignees
Labels
area-front-end Use area-front-end for front end / CFE / kernel format related issues. front-end-fasta P1 A high priority bug; for example, a single project is unusable or has many test failures type-task A well-defined stand-alone task

Comments

@lrhn
Copy link
Member

lrhn commented Sep 28, 2017

This is the Front-end specific issue tracking #30921.

The front-end needs to handle the new syntax and provide kernel code that treats constructor invocations equivalently whether they use the new prefix or not, and code that generates the same constant values whether nested const prefixes are used.

@lrhn lrhn added the type-task A well-defined stand-alone task label Sep 28, 2017
@lrhn lrhn added this to the 2.0-beta1 milestone Sep 28, 2017
@lrhn lrhn changed the title Parsing of optional new and const. Front-end handling of optional new and const. Sep 28, 2017
@sigmundch sigmundch added front-end-fasta area-front-end Use area-front-end for front end / CFE / kernel format related issues. labels Sep 28, 2017
@peter-ahe-google
Copy link
Contributor

We will not start implementation of this feature until the front-end is on par with the VM in terms of test passes.

@sigmundch sigmundch removed their assignment Nov 29, 2017
@jensjoha jensjoha added the P1 A high priority bug; for example, a single project is unusable or has many test failures label Jan 11, 2018
@kmillikin
Copy link

We have an initial implementation of this feature but it is not yet complete. We fail on the following tests in the language_2 suite for various reasons (most of them seem due to const contexts):

implicit_creation/implicit_const_context_constructor_generic_named_test: CompileTimeError
implicit_creation/implicit_const_context_constructor_generic_test: CompileTimeError
implicit_creation/implicit_const_context_constructor_named_test: CompileTimeError
implicit_creation/implicit_const_context_constructor_test: CompileTimeError
implicit_creation/implicit_const_context_list_test: CompileTimeError
implicit_creation/implicit_const_context_map_test: CompileTimeError
implicit_creation/implicit_const_context_prefix_constructor_generic_named_test: CompileTimeError
implicit_creation/implicit_const_context_prefix_constructor_generic_test: CompileTimeError
implicit_creation/implicit_const_context_prefix_constructor_named_test: CompileTimeError
implicit_creation/implicit_const_context_prefix_constructor_test: CompileTimeError
implicit_creation/implicit_new_constructor_generic_named_test: CompileTimeError
implicit_creation/implicit_new_or_const_generic_test: CompileTimeError
implicit_creation/implicit_new_prefix_constructor_generic_named_test: CompileTimeError

@peter-ahe-google
Copy link
Contributor

Change 41261 should fix the remaining compile-time errors.

@peter-ahe-google
Copy link
Contributor

Along with change 41260 which modifies the tests to not rely on metadata on local functions. Metadata on local functions has never been implemented in dart2js, so we're not deeming that important right now. I've filed #32193 to track this.

@dgrove dgrove modified the milestones: (Please move issues from the milestone) 2.0-beta1, Dart2 Beta 3 Mar 21, 2018
@a-siva
Copy link
Contributor

a-siva commented Mar 29, 2018

This issue was opened to track the implementation of optional 'new' and 'const' feature, Now that the feature has landed can this issue be closed and bugs if any be tracked in issues specific to each bug.

@JekCharlsonYu JekCharlsonYu removed this from the Dart2 Beta 3 milestone Mar 29, 2018
@JekCharlsonYu
Copy link
Contributor

Removed this from Dart2 Beta3 milestone too. Thanks.

@peter-ahe-google
Copy link
Contributor

Thank you, @a-siva

@peter-ahe-google
Copy link
Contributor

Actually, I'd forgotten to land this https://dart-review.googlesource.com/c/sdk/+/41261

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-front-end Use area-front-end for front end / CFE / kernel format related issues. front-end-fasta P1 A high priority bug; for example, a single project is unusable or has many test failures type-task A well-defined stand-alone task
Projects
None yet
Development

No branches or pull requests

8 participants