-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Comments
new
and const
.new
and const
.
We will not start implementation of this feature until the front-end is on par with the VM in terms of test passes. |
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):
|
Change 41261 should fix the remaining compile-time errors. |
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. |
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. |
Removed this from Dart2 Beta3 milestone too. Thanks. |
Thank you, @a-siva |
Actually, I'd forgotten to land this https://dart-review.googlesource.com/c/sdk/+/41261 |
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 nestedconst
prefixes are used.The text was updated successfully, but these errors were encountered: