Fix async awaiter result identity - #2758
Merged
Merged
Conversation
Key pooled awaiter fields by their emitted symbolic type so erased Task results, including tuples, retain distinct state-machine field and local identities.
Encode arity-eight and larger tuples with canonical nested ValueTuple TRest shapes, including imported and symbolic async result signatures, tuple construction, and ItemN access.
This was referenced Jul 23, 2026
Closed
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
ValueTuple<T1,...,T7,TRest>construction, signatures, imported flattening, andItemNaccessValidation
Deferred
Parser/binder already represented arity-8+ tuples, so no prerequisite issue was needed. Interpreter behavior remains unchanged per the requested compiler/emitter scope.
Fixes #2750