Skip to content

[vm] Async return type FutureOr<Object> returns Future<dynamic> #54316

New issue

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

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

Already on GitHub? # to your account

Closed
eernstg opened this issue Dec 12, 2023 · 0 comments
Closed

[vm] Async return type FutureOr<Object> returns Future<dynamic> #54316

eernstg opened this issue Dec 12, 2023 · 0 comments
Assignees
Labels
area-vm Use area-vm for VM related issues, including code coverage, and the AOT and JIT backends. P3 A lower priority bug or feature request triaged Issue has been triaged by sub team

Comments

@eernstg
Copy link
Member

eernstg commented Dec 12, 2023

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.

@eernstg 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
@alexmarkov alexmarkov self-assigned this Dec 12, 2023
@eernstg eernstg changed the title [vm] Return type FutureOr<Object> returns Future<dynamic> [vm] Async return type FutureOr<Object> returns Future<dynamic> Dec 13, 2023
@a-siva a-siva added P3 A lower priority bug or feature request triaged Issue has been triaged by sub team labels Dec 14, 2023
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
area-vm Use area-vm for VM related issues, including code coverage, and the AOT and JIT backends. P3 A lower priority bug or feature request triaged Issue has been triaged by sub team
Projects
None yet
Development

No branches or pull requests

3 participants