Skip to content

Dart throws a compile error when async function with Future<bool> return type returns dynamic. #42236

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

Closed
iarkh opened this issue Jun 9, 2020 · 0 comments
Labels
legacy-area-front-end Legacy: Use area-dart-model instead. type-bug Incorrect behavior (everything from a crash to more subtle misbehavior)

Comments

@iarkh
Copy link
Contributor

iarkh commented Jun 9, 2020

Dart VM version: 2.9.0-13.0.dev (dev) (Fri May 29 15:59:05 2020 +0200) on "windows_x64"

This issue is related with SDK Issues #41266, #41437, as well as with co19 issues 603 and 703.

Seems like after the 941 the following code should not throw compile error:

import "dart:async";
dynamic getNull() => null;
Future<bool> test1() async => await getNull();
main() {}

However, still dart behave in such a way.

Sample output is:

$> dart --enable-experiment=non-nullable test.dart
test.dart:3:31: Error: A value of type 'Future<dynamic>' can't be assigned to a variable of type 'FutureOr<bool>'.

  • 'Future' is from 'dart:async'.
  • 'FutureOr' is from 'dart:async'.
    Future<bool> test1() async => await getNull();
@lrhn lrhn added legacy-area-front-end Legacy: Use area-dart-model instead. type-bug Incorrect behavior (everything from a crash to more subtle misbehavior) labels Jun 9, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
legacy-area-front-end Legacy: Use area-dart-model instead. type-bug Incorrect behavior (everything from a crash to more subtle misbehavior)
Projects
None yet
Development

No branches or pull requests

2 participants