fix: Fix struct or tuple field assignment failing with generics #1317
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 #1315
Description
Summary of changes
Fixes an issue where we forgot to call
.follow_bindings()
before matching on a type to see if it was a struct, tuple, or neither. This led to the issue described in #1315 where the compiler did not see the type as a struct and thus thought there was no field of the given name.Dependency additions / changes
None
Test additions / changes
None
Checklist
cargo fmt
with default settings.Documentation needs
Additional context