ast/tests: Repeat type resolution for arguments in lambda to fix #3315 and fix #3308 #3318
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.
The type resolution has top be repeated for actual arguments in a lambda, lazy or partial call since the outer feature has changed.
For this to work, the code that assigns the initial value to a field must be created later, i.e, not during
resolveTypes
but in phasesyntaxSugar1
.The issue from #3315 is no longer commented out in tests/reg_issue3308 and an even simpler example was added as well. This PR also adds new test cases with outer feature being a function and not a constructor. This includes a commented-out version of the example in #3324, which does not work yet.