Future produced by async function has wrong type argument #49424
Labels
area-vm
Use area-vm for VM related issues, including code coverage, FFI, and the AOT and JIT backends.
cherry-pick-candidate
Candidates to be cherry-picked
type-bug
Incorrect behavior (everything from a crash to more subtle misbehavior)
Originally posted by @TimWhiting in #49345 (comment)
A future related test is failing on flutter/dart master with the fpdart library, found while creating this pull request to fix mixin breaking changes to work on master. I believe I'm running with a new enough sdk to incorporate the soundness fix.
SandroMaglione/fpdart#42
This is the test.
This is the relevant bit of Task
dart version:
output
Standalone repo with just the above code, able to reproduce:
https://github.com/TimWhiting/dart_fail_future
Analyzer shows the correct type when hovering over the future returned from Task.run()
The text was updated successfully, but these errors were encountered: