[breaking change] Null safety changes #40686
Labels
area-meta
breaking-change-request
This tracks requests for feedback on breaking changes
NNBD
Issues related to NNBD Release
Milestone
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.
Language
Core libraries
dart:core
RuneIterator
class has some members which returnnull
in the state where the iterator has no "current" element; they will now return -1 or an empty stringString.fromEnvironment
andint.fromEnvironment
const constructors will have a non-null
defaultValue
default value.That will also make it not inherit the message getter.
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 toFuture<void>
.dart:io
:The text was updated successfully, but these errors were encountered: