This is a meta-issue summarizing breaking changes made as part of realizing the null safety feature.
We are planning on landing these breaking changes fairly soon, and this in advance of the full null safety feature to ensure that we have sufficient time to uncover any unanticipated consequences.
Please comment on the issues list below if you expect these changes to cause severe problems for your code.
dart:core
RuneIterator class has some members which return null in the state where the iterator has no "current" element; they will now return -1 or an empty stringString.fromEnvironment and int.fromEnvironment const constructors will have a non-null defaultValue default value.dart:async:
runZoned method will now not catch synchronously thrown errors even when given an error handler.StreamSubscription.cancel method's return type is changed to Future<void>.dart:io:
| Franklin Yow | | Program Manager | | fran...@google.com | | 206-531-1401 |