Fix explicit types in for loops #2440
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This fixes a long hidden bug where using explicit types in a for loop (technically supported because the loop binding variable is parsed as a pattern just like bindings for let-stmts and callable params) would cause the type for the binding to be unknown and propagate as an error type through the code.
idavis
approved these changes
May 20, 2025
ScottCarda-MS
approved these changes
May 20, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This fixes a long hidden bug where using explicit types in a for loop (technically supported because the loop binding variable is parsed as a pattern just like bindings for let-stmts and callable params) would cause the type for the binding to be unknown and propagate as an error type through the code.