Dart type checking became more strict

[drewwarren]

I have a function

double get packedPercent =>
      deadline.totalItems == 0 ? 0 : packedCount / deadline.totalItems;

This function used to work fine, even when deadline.totalItems was 0. Now it fails when a type error when deadline.totalItems is 0.

I'm guessing this is because I am returning an int 0 instead of a double 0.0.

I do not get any output from dart analysis related to this, even when using https://github.com/raw/flutter/flutter/master/.analysis_options

StoreManager: ══╡ EXCEPTION CAUGHT BY WIDGETS LIBRARY ╞═══════════════════════════════════════════════════════════
StoreManager: The following assertion was thrown building _Deadline:
StoreManager: type 'int' is not a subtype of type 'double' of 'function result' where
StoreManager:   int is from dart:core
StoreManager:   double is from dart:core
StoreManager: Either the assertion indicates an error in the framework itself, or we should provide substantially
StoreManager: more information in this error message to help you determine and fix the underlying cause.
StoreManager: In either case, please report this assertion by filing a bug on GitHub:
StoreManager:   https://github.com/flutter/flutter/issues/new
StoreManager: When the exception was thrown, this was the stack:
StoreManager: #0      _Deadline.packedPercent (lib/routes/dashboard/deadlines.dart:74)
StoreManager: #1      _Deadline.packedPercentAndTimeLeft (lib/routes/dashboard/deadlines.dart:137)
StoreManager: #2      _Deadline.build (lib/routes/dashboard/deadlines.dart:93)
StoreManager: #3      ComponentElement.performRebuild (package:flutter/src/widgets/framework.dart:2027)
StoreManager: #4      BuildableElement.rebuild (package:flutter/src/widgets/framework.dart:1941)
StoreManager: #5      ComponentElement._firstBuild (package:flutter/src/widgets/framework.dart:2013)
StoreManager: #6      ComponentElement.mount (package:flutter/src/widgets/framework.dart:2008)
StoreManager: #7      Element.inflateWidget (package:flutter/src/widgets/framework.dart:1584)
StoreManager: #8      MultiChildRenderObjectElement.mount (package:flutter/src/widgets/framework.dart:2780)
StoreManager: #9      Element.inflateWidget (package:flutter/src/widgets/framework.dart:1584)
StoreManager: #10     Element.updateChild (package:flutter/src/widgets/framework.dart:1461)
StoreManager: #11     ComponentElement.performRebuild (package:flutter/src/widgets/framework.dart:2039)
StoreManager: #12     BuildableElement.rebuild (package:flutter/src/widgets/framework.dart:1941)
...

[eseidelGoogle]

So this is a recent VM change, which was picked up in a flutter/engine roll. Is this expected @a-siva?

[eseidelGoogle]

CC @pq since the analyzer doesn't warn about this?

[Hixie]

Does your .analysis_options file turn on all the type checking?
I'm pretty sure this has never worked before? We've asked for it to work for a while (it's on the Flutter team's "Dart wishlist"), so I'd be surprised if it did work before...

[pq]

cc @bwilkerson @jmesserly who may have better insight into the analysis side of things.

[bwilkerson]

Was this error produced by running the AOT compiler?

[jmesserly]

This is just a checked mode failure. This hasn't ever worked in Dart.

$ cat test.dart

double get packedPercent => 0;
main() { print(packedPercent); }

$ dartanalyzer test.dart

Analyzing [test.dart]...
[warning] The return type 'int' is not a 'double', as defined by the method 'packedPercent'. (test.dart, line 1, col 29)
1 warning found.

$ dartanalyzer --strong test.dart

Analyzing [test.dart]...
[error] The return type 'int' is not a 'double', as defined by the method 'packedPercent'. (test.dart, line 1, col 29)
1 error found.

$ dart -c test.dart

Unhandled exception:
type 'int' is not a subtype of type 'double' of 'function result' where
  int is from dart:core
  double is from dart:core

#0      packedPercent (test.dart:1:29)
#1      main (test.dart:2:16)
#2      _startIsolate.<anonymous closure> (dart:isolate-patch/isolate_patch.dart:261)
#3      _RawReceivePortImpl._handleMessage (dart:isolate-patch/isolate_patch.dart:148)

[drewwarren]

void main() {
  print(test(1));
  print(test(2));
  print(test(0));
}

double test(int a) => a == 0 ? 0 : 1 / a;

This currently runs on dartpad with no issues and no analyzer warnings. It will fail on the VM flutter uses.

CONSOLE

1
0.5
0

https://dartpad.dartlang.org/53bd8d3a960c49b0f8f22b80362aec13

[Hixie]

dart2js has limitations with respect to how closely it implements dart's rules about numbers, due to JS only having one number type.

[sethladd]

Not sure if analyzer knows what to do here, when ternary operator returns either int or double, and the function is marked to return a double. I'd expect an analyzer warning, regardless of later being compiled with dart2js.

cc @bwilkerson ?

[jmesserly]

They do not appear to have "checked mode" turned on in dartpad. So type annotations are more or less ignored.

Not sure if analyzer knows what to do here, when ternary operator returns either int or double, and the function is marked to return a double. I'd expect an analyzer warning, regardless of later being compiled with dart2js.

@sethladd Analyzer knows what to do. It concludes "num", which is then implicitly downcast to "double". All of our modes allow it, if you want to disable downcasts use the recently introduced (in 1.19) --no-implicit-casts flag of strong mode. See:

http://news.dartlang.org/2016/08/dart-119-improved-developer-experiences.html

[jmesserly]

Oops I should've linked to the changelog:
https://github.com/dart-lang/sdk/blob/52ecac4ed50cd25d5cf1def3e9bfcf1c6a83d133/CHANGELOG.md#strong-mode

[sethladd]

@jmesserly kk, thanks! (all these modes and options and lints and features are making my head swim)

[drewwarren]

~$ dart --version

Dart VM version: 1.19.0-dev.5.0 (Wed Aug 10 09:29:58 2016) on "macos_x64"

~$ dartanalyzer --version

dartanalyzer version 1.19.0-dev.5.0~$ 

~$ cat test.dart

void main() {
 print(test(2));
 print(test(0));
}

double test(int a) => a == 0 ? 0 : 1 / a;

~$ dartanalyzer test.dart

Analyzing [test.dart]...
No issues found

~$ dartanalyzer --strong test.dart

Analyzing [test.dart]...
No issues found

~$ dart test.dart

0.5
0

~$ dart -c test.dart

0.5
Unhandled exception:
type 'int' is not a subtype of type 'double' of 'function result' where
  int is from dart:core
  double is from dart:core

#0      test (file:///Users/drewwarren/test.dart:6:23)
#1      main (file:///Users/drewwarren/test.dart:3:8)
#2      _startIsolate.<anonymous closure> (dart:isolate-patch/isolate_patch.dart:261)
#3      _RawReceivePortImpl._handleMessage (dart:isolate-patch/isolate_patch.dart:148)

[jmesserly]

@jmesserly kk, thanks! (all these modes and options and lints and features are making my head swim)

yeah no kidding!

If it helps to know, things will get better :). Strong mode will be "the only mode". Things like --no-implicit-casts are ways for us to gracefully introduce stricter checking we think is a good idea, and determine if it can be rolled into strong mode.