-
Notifications
You must be signed in to change notification settings - Fork 1.7k
for-in inference broken in dev.17.0 #31884
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
legacy-area-analyzer
Use area-devexp instead.
type-bug
Incorrect behavior (everything from a crash to more subtle misbehavior)
Comments
natebosch
added a commit
to dart-lang/build
that referenced
this issue
Jan 12, 2018
Work around for dart-lang/sdk#31884 in the dev.17.0 version of the SDK
natebosch
added a commit
to dart-lang/build
that referenced
this issue
Jan 12, 2018
Work around for dart-lang/sdk#31884 in the dev.17.0 version of the SDK
Also, shouldn't the |
Yes, we're using |
natebosch
added a commit
to dart-archive/graphs
that referenced
this issue
Jan 16, 2018
Workaround for dart-lang/sdk#31884 in the dev.17.0 version of the SDK.
natebosch
added a commit
to dart-archive/graphs
that referenced
this issue
Jan 17, 2018
Workaround for dart-lang/sdk#31884 in the dev.17.0 version of the SDK.
Seems to be fixed in dev.18 |
dcharkes
pushed a commit
to dart-lang/tools
that referenced
this issue
May 23, 2023
Workaround for dart-lang/sdk#31884 in the dev.17.0 version of the SDK.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
legacy-area-analyzer
Use area-devexp instead.
type-bug
Incorrect behavior (everything from a crash to more subtle misbehavior)
When the iterable in a for-in loop needs inference the variable doesn't get the right inferred type. Examples shown with
implicit-casts: false
, but the broken inference can cause problems in other ways without that option - such as no good feedback in the IDEAn example:
Broken:
Working if you add a variable so the type is already inferred:
Also works if you force the type of the loop variable
cc @munificent
The text was updated successfully, but these errors were encountered: