-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Specify strong mode "top level" inference #27499
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
Labels
area-specification (deprecated)
Deprecated: use area-language and a language- label.
language-strong-mode-polish
Comments
Proposal is now here for consideration: #28218 . |
Tracking bug for implementation here: #28219 |
Can we close this one? |
No Dart 2 milestone: This is now considered a subtask of #31228, which has a Dart 2 milestone. |
4 tasks
Can this be closed? |
I have a pull request out with a specification for this. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
area-specification (deprecated)
Deprecated: use area-language and a language- label.
language-strong-mode-polish
Uh oh!
There was an error while loading. Please reload this page.
We've spent a lot of time discussing strategies around how we handle type inference of "top level" declarations—top level variables and static fields. There is what strong mode currently implements, and the revised rules we've considered informally.
The next step is to write up the set of rules we want to commit to.
Edit by @eernstg Feb 2018: Note that this is now essentially one of the subtasks of #31228.
The text was updated successfully, but these errors were encountered: