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.
Related issue(s)
Resolves #1309
Description
Summary of changes
A parser bug parsing fields using
ident()
instead offield_name()
(which is an ident or integer literal) lead to assignment to tuple fields not being possible. This was overlooked before, as the relevant code to handle tuple-field assignments was not in the type checker either. To fix this I've merged the code that handles tuple field assignments and tuple field access (a normal a.b expression not in an LValue context) so that this will not happen again. I've also slightly improved the error message if a user accesses a tuple field that is out of bounds.Dependency additions / changes
Test additions / changes
Checklist
cargo fmt
with default settings.Documentation needs
Additional context
BEGIN_COMMIT_OVERRIDE
fix: Fix parser error preventing assignments to tuple fields (#1318)
END_COMMIT_OVERRIDE