Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix crash when inferring multiple assignment with overloaded function #10689

Merged
merged 1 commit into from Jun 22, 2021

Conversation

JukkaL
Copy link
Collaborator

@JukkaL JukkaL commented Jun 22, 2021

When using lvalue context to re-infer call to an overloaded function,
the inferred tuple type can switch to Any. Defensively accept this. It
probably means that an Any component in argument types causes ambiguity.

Fixes #10653.

When using lvalue context to re-infer call to an overloaded function,
the inferred tuple type can switch to Any. Defensively accept this. It
probably means that an Any component in argument types causes ambiguity.

Fixes #10653.
Copy link
Member

@ilevkivskyi ilevkivskyi left a comment

Makes sense.

Copy link
Collaborator

@TH3CHARLie TH3CHARLie left a comment

I wouldn't come up with fixing here, nice!

@JukkaL JukkaL merged commit 3319826 into master Jun 22, 2021
6 checks passed
@JukkaL JukkaL deleted the await-tuple-crash branch Jun 22, 2021
JukkaL added a commit that referenced this pull request Jun 22, 2021
…#10689)

When using lvalue context to re-infer call to an overloaded function,
the inferred tuple type can switch to Any. Defensively accept this. It
probably means that an Any component in argument types causes ambiguity.

Fixes #10653.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0.902 crashes on tuple assignment
3 participants