You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
eernstg opened this issue
Dec 12, 2023
· 0 comments
Assignees
Labels
area-vmUse area-vm for VM related issues, including code coverage, and the AOT and JIT backends.P3A lower priority bug or feature requesttriagedIssue has been triaged by sub team
This is the vm specific issue for the behavior reported in #54311, which has the details (some details here: #54311 (comment)).
The main point is that we can have an async function with declared return type FutureOr<Object> that actually returns a Future<dynamic> (it should return a Future<Object>). The Kernel code which is generated for the example program seems to be correct, so the issue seems to be caused by the processing of this Kernel code in backends.
The text was updated successfully, but these errors were encountered:
eernstg
added
the
area-vm
Use area-vm for VM related issues, including code coverage, and the AOT and JIT backends.
label
Dec 12, 2023
eernstg
changed the title
[vm] Return type FutureOr<Object> returns Future<dynamic>
[vm] Async return type FutureOr<Object> returns Future<dynamic>Dec 13, 2023
area-vmUse area-vm for VM related issues, including code coverage, and the AOT and JIT backends.P3A lower priority bug or feature requesttriagedIssue has been triaged by sub team
This is the vm specific issue for the behavior reported in #54311, which has the details (some details here: #54311 (comment)).
The main point is that we can have an async function with declared return type
FutureOr<Object>
that actually returns aFuture<dynamic>
(it should return aFuture<Object>
). The Kernel code which is generated for the example program seems to be correct, so the issue seems to be caused by the processing of this Kernel code in backends.The text was updated successfully, but these errors were encountered: