-
Notifications
You must be signed in to change notification settings - Fork 661
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
[Bug] Type mismatch when awaiting Future from tuple #28312
Comments
Adding another example.
|
I'm running into a slightly different issue now. If two different Futures are included in tuples, it duplicates one of them. Given this program:
With the fix on the
where I would expect the finalize to be
|
@d0cd I can confirm this problem. We independently tried a similar patch and this has broken type inference exactly as Chris has reported. So at the moment we have to manually patch our compiled code. Are there any ETAs for a fix? |
@akalmykov the team is working on a fix, however, you can get around this issue by destructuring your tuple |
Attaching a test case
|
🐛 Bug Report
When calling a function that returns a
Future
as part of a tuple (e.g.transfer_public_to_private
) the compiler failsSteps to Reproduce
Code snippet to reproduce
Stack trace & error message
Expected Behavior
The compiler should recognize the Future as the correct type
Your Environment
The text was updated successfully, but these errors were encountered: