Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
>=2.12.0 <3.0.0
-><4.0.0
Release Notes
dart-lang/sdk (dart)
v3.4.4
Compare Source
v3.4.3
Compare Source
v3.4.2
Compare Source
v3.4.1
Compare Source
v3.4.0
Compare Source
Language
Dart 3.4 makes improvements to the type analysis of conditional expressions
(
e1 ? e2 : e3
), if-null expressions (e1 ?? e2
), if-null assignments(
e1 ??= e2
), and switch expressions (switch (e) { p1 => e1, ... }
). To takeadvantage of these improvements, set your package's
SDK constraint lower bound to 3.4 or greater
(
sdk: '^3.4.0'
).Breaking Change #54640: The pattern context type schema for
cast patterns has been changed from
Object?
to_
(the unknowntype), to align with the specification. This change is not expected
to make any difference in practice.
Breaking Change #54828: The type schema used by the compiler front end
to perform type inference on the operand of a null-aware spread operator
(
...?
) in map and set literals has been made nullable, to match whatcurrently happens in list literals. This makes the compiler front end behavior
consistent with that of the analyzer. This change is expected to be very low
impact.
Libraries
dart:async
ParallelWaitError
to get some meta-information thatit can expose in its
toString
, and theIterable<Future>.wait
and(Future,...,Future).wait
extension methods now provide that information.Should make a
ParallelWaitError
easier to log.dart:cli
waitFor
is removed in 3.4.dart:ffi
Struct.create
andUnion.create
to create struct and union viewsof the sequence of bytes stored in a subtype of
TypedData
.dart:io
Breaking change #53863:
Stdout
has a new fieldlineTerminator
,which allows developers to control the line ending used by
stdout
andstderr
. Classes thatimplement Stdout
must define thelineTerminator
field. The default semantics of
stdout
andstderr
are not changed.Deprecates
FileSystemDeleteEvent.isDirectory
, which always returnsfalse
.dart:js_interop
Fixes an issue with several comparison operators in
JSAnyOperatorExtension
that were declared to return
JSBoolean
but really returnedbool
. This ledto runtime errors when trying to use the return values. The implementation now
returns a
JSBoolean
to align with the interface. See issue #55024 formore details.
Added
ExternalDartReference
and related conversion functionstoExternalReference
andtoDartObject
. This is a faster alternative toJSBoxedDartObject
, but with fewer safety guarantees and fewerinteroperability capabilities. See #55187 for more details.
On dart2wasm,
JSBoxedDartObject
now is an actual JS object that wraps theopaque Dart value instead of only externalizing the value. Like the JS
backends, you'll now get a more useful error when trying to use it in another
Dart runtime.
Added
isA
helper to make type checks easier with interop types. See#54138 for more details.
dart:typed_data
BREAKING CHANGE #53218 #53785: The unmodifiable view classes for
typed data are deprecated.
To create an unmodifiable view of a typed-data object, use the
asUnmodifiableView()
methods added in Dart 3.3:The reason for this change is to allow more flexibility in the implementation
of typed data, so the native and web platforms can use different strategies
to ensure that typed data has good performance.
The deprecated types will be removed in Dart 3.5.
Tools
Analyzer
Improved code completion. Fixed over 50% of completion correctness bugs,
tagged
analyzer-completion-correctness
in the issuetracker.
Support for new annotations introduced in version 1.14.0 of the meta
package.
Support for the [
@doNotSubmit
][@doNotSubmit] annotation, noting that any usage of anannotated member should not be submitted to source control.
Support for the [
@mustBeConst
][@mustBeConst] annotation, which indicates that anannotated parameter only accepts constant arguments.
Linter
unnecessary_library_name
][unnecessary_library_name] lint.missing_code_block_language_in_doc_comment
][missing_code_block_language_in_doc_comment] lint.Compilers
value
""
for alldart.library.foo
strings, wheredart:foo
is not anavailable library. Instead there will only be entries for the available
libraries, like
dart.library.core
, where the value was, and still is,"true"
. This should have no effect onconst bool.fromEnvironment(...)
orconst String.fromEnvironment(...)
without adefaultValue
argument, anargument which was always ignored previously. It changes the behavior of
const bool.hasEnvironment(...)
on such an input, away from always beingtrue
and therefore useless.DevTools
To learn more, check out the release notes for versions
2.32.0 and 2.33.0.
Pub
Dependency resolution and
dart pub outdated
will now surface if a dependencyis affected by a security advisory, unless the advisory is listed under a
ignored_advisories
section in thepubspec.yaml
file. To learn more aboutpub's support for security advisories, visit
dart.dev/go/pub-security-advisories.
path
-dependencies insidegit
-dependencies are now resolved relative to thegit repo.
All
dart pub
commands can now be run from any subdirectory of a project. Pubwill find the first parent directory with a
pubspec.yaml
and operaterelative it.
New command
dart pub unpack
that downloads a package from pub.dev andextracts it to a subfolder of the current directory.
This can be useful for inspecting the code, or playing with examples.
Dart Runtime
Dart VM flags and options can now be provided to any executable generated
using
dart compile exe
via theDART_VM_OPTIONS
environment variable.DART_VM_OPTIONS
should be set to a list of comma-separated flags and optionswith no whitespace. Options that allow for multiple values to be provided as
comma-separated values are not supported (e.g.,
--timeline-streams=Dart,GC,Compiler
).Example of a valid
DART_VM_OPTIONS
environment variable:Dart VM no longer supports external strings:
Dart_IsExternalString
,Dart_NewExternalLatin1String
andDart_NewExternalUTF16String
functions areremoved from Dart C API.
v3.3.4
Compare Source
This is a patch release that:
the enclosing library's
@JS
annotation were actually using the invocation'senclosing library's
@JS
annotation. (issue #55430).v3.3.3
Compare Source
This is a patch release that:
v3.3.2
Compare Source
This is a patch release that:
of their context in the code restored from dill files, causing crashes in the
incremental compiler whenever it restored a typedef from dill such that the
typedef contained a generic function type on its right-hand side (issue
#55158).
resolved in initializers of extension types (issue #55194).
DateTime.timeZoneName
on Windows, which was checking whether current date is in the summer or
standard time rather than checking if the given moment is in the summer or
standard time (issue #55240).
v3.3.1
Compare Source
This is a patch release that:
extension types would fail to compile without an
@JS
annotation on thelibrary (issue #55057).
operand of an
await
expression, unless the extension type itself implementsFuture
(issue #55095).v3.3.0
Compare Source
Language
Dart 3.3 adds extension types to the language. To use them, set your
package's [SDK constraint][language version] lower bound to 3.3 or greater
(
sdk: '^3.3.0'
).Extension types
An extension type wraps an existing type with a different, static-only
interface. It works in a way which is in many ways similar to a class that
contains a single final instance variable holding the wrapped object, but
without the space and time overhead of an actual wrapper object.
Extension types are introduced by extension type declarations. Each
such declaration declares a new named type (not just a new name for the
same type). It declares a representation variable whose type is the
representation type. The effect of using an extension type is that the
representation (that is, the value of the representation variable) has
the members declared by the extension type rather than the members declared
by its "own" type (the representation type). Example:
The declaration
Meters
is an extension type that has representation typeint
. It introduces an implicit constructorMeters(int value);
and agetter
int get value
.m
andm.value
is the very same object, butm
has type
Meters
andm.value
has typeint
. The point is thatm
has the members of
Meters
andm.value
has the members ofint
.Extension types are entirely static, they do not exist at run time. If
o
is the value of an expression whose static type is an extension type
E
with representation type
R
, theno
is just a normal object whoserun-time type is a subtype of
R
, exactly like the value of an expressionof type
R
. Also the run-time value ofE
isR
(for example,E == R
is true). In short: At run time, an extension type is erased to the
corresponding representation type.
A method call on an expression of an extension type is resolved at
compile-time, based on the static type of the receiver, similar to how
extension method calls work. There is no virtual or dynamic dispatch. This,
combined with no memory overhead, means that extension types are zero-cost
wrappers around their representation value.
While there is thus no performance cost to using extension types, there is
a safety cost. Since extension types are erased at compile time, run-time
type tests on values that are statically typed as an extension type will
check the type of the representation object instead, and if the type check
looks like it tests for an extension type, like
is Meters
, it actuallychecks for the representation type, that is, it works exactly like
is int
at run time. Moreover, as mentioned above, if an extension type is used as
a type argument to a generic class or function, the type variable will be
bound to the representation type at run time. For example:
Extension types are useful when you are willing to sacrifice some run-time
encapsulation in order to avoid the overhead of wrapping values in
instances of wrapper classes, but still want to provide a different
interface than the wrapped object. An example of that is interop, where you
may have data that are not Dart objects to begin with (for example, raw
JavaScript objects when using JavaScript interop), and you may have large
collections of objects where it's not efficient to allocate an extra object
for each element.
Other changes
Breaking Change #54056: The rules for private field promotion have
been changed so that an abstract getter is considered promotable if there are
no conflicting declarations. There are no conflicting declarations if
there are no non-final fields, external fields, concrete getters, or
noSuchMethod
forwarding getters with the same name in the same library.This makes the implementation more consistent and allows
type promotion in a few rare scenarios where it wasn't previously allowed.
It is unlikely, but this change could cause a breakage by changing
an inferred type in a way that breaks later code. For example:
Affected code can be fixed by adding an explicit type annotation.
For example, in the above snippet,
var x
can be changed toint? x
.It's also possible that some continuous integration configurations might fail
if they have been configured to treat warnings as errors, because the expanded
type promotion could lead to one of the following warnings:
unnecessary_non_null_assertion
unnecessary_cast
invalid_null_aware_operator
These warnings can be addressed in the usual way, by removing the unnecessary
operation in the first two cases, or changing
?.
to.
in the third case.To learn more about other rules surrounding type promotion,
check out the guide on Fixing type promotion failures.
Libraries
dart:core
String.fromCharCodes
now allowstart
andend
to be after the end ofthe
Iterable
argument, just likeskip
andtake
does on anIterable
.dart:ffi
@Native
can now be used on fields.Native.addressOf
.elementAt
pointer arithmetic extension methods oncore
Pointer
types are now deprecated.Migrate to the new
-
and+
operators instead.@FfiNative
annotation has been removed.Usages should be updated to use the
@Native
annotation.dart:js_interop
like
JSAny
were previously represented using a custom erasure of@staticInterop
types that were compiler-specific. They are now representedas extension types where their representation types are compiler-specific.
This means that user-defined
@staticInterop
types that implementedJSAny
or
JSObject
can no longer do so and need to useJSObject.fromInteropObject
. Going forward, it's recommended to use extensiontypes to define interop APIs. Those extension types can still implement JS
types.
JSArray
andJSPromise
are now generictypes whose type parameter is a subtype of
JSAny?
. Conversions to and fromthese types are changed to account for the type parameters of the Dart or JS
type, respectively.
dart:js_interop
extensionmembers are moved to different extensions on the same type or a supertype to
better organize the API surface. See
JSAnyUtilityExtension
andJSAnyOperatorExtension
for the new extensions. This shouldn't make adifference unless the extension names were explicitly used.
importModule
to allow users to dynamically import modules using the JSimport()
expression.dart:js_interop_unsafe
has
helper to makehasProperty
calls more concise.dart:typed_data
BREAKING CHANGE (https://github.com/dart-lang/sdk/issues/53218) The
unmodifiable view classes for typed data are deprecated. Instead of using the
constructors for these classes to create an unmodifiable view, e.g.
use the new
asUnmodifiableView()
methods:The reason for this change is to allow more flexibility in the implementation
of typed data so the native and web platforms can use different strategies
for ensuring typed data has good performance.
The deprecated types will be removed in a future Dart version.
dart:nativewrappers
base
sothat none of their subtypes can be implemented. Implementing subtypes can lead
to crashes when passing such native wrapper to a native call, as it will try
to unwrap a native field that doesn't exist.
Tools
Dart command line
dart create
command now uses v3 ofpackage:lints
,including multiple new recommended lints by default.
To learn more about the updated collection of lints,
check out the
package:lints
3.0.0 changelog entry.DevTools
To learn more, check out the release notes for versions
2.29.0, 2.30.0,
and 2.31.0.
Wasm compiler (dart2wasm)
dart:js_util
,package:js
, anddart:js
are now disallowed from being imported when compiling with
dart2wasm
. Preferusing
dart:js_interop
anddart:js_interop_unsafe
.Development JavaScript compiler (DDC)
Type arguments of
package:js
interop types are now printed asany
insteadof being omitted. This is simply a change to the textual representation of
package js types that have type arguments. These type arguments are still
completely ignored by the type system at runtime.
Removed "implements <...>" text from the Chrome custom formatter display for
Dart classes. This information provides little value and keeping it imposes an
unnecessary maintenance cost.
Production JavaScript compiler (dart2js)
The
Invocation
that is passed tonoSuchMethod
will no longer have aminified
memberName
, even when dart2js is invoked with--minify
.See #54201 for more details.
Analyzer
pubspec.yaml
files byadding an
# ignore: <diagnostic_id>
comment.dart doc
comment directives are now reported.flutter_style_todos
][flutter_style_todos] lint now has a quick fix.Linter
iterable_contains_unrelated_type
andlist_remove_unrelated_type
lints.Consider migrating to the expanded
[
collection_methods_unrelated_type
][collection_methods_unrelated_type] lint.always_require_non_null_named_parameters
avoid_returning_null
,avoid_returning_null_for_future
v3.2.6
Compare Source
v3.2.5
Compare Source
v3.2.4
Compare Source
v3.2.3
Compare Source
This is a patch release that:
(issue #54232).
environments that don't support the integer division
instructions or x86-64 environments that don't support
SSE4.1 (issue #54215).
v3.2.2
Compare Source
This is a patch release that:
Adjusts the nullablity computations in the implementation of the
upper bound algorithm in the compiler frontend (issue #53999).
Fixes missing closure code completion entries for function parameters
for LSP-based editors like VS Code (issue #54112).
v3.2.1
Compare Source
This is a patch release that:
Fixes the left/mobile sidebar being empty on non-class pages
in documentation generated with
dart doc
(issue #54073).Fixes a JSON array parsing bug that causes a segmentation fault when
flutter test
is invoked with the--coverage
flag(SDK issue #54059, Flutter issue #124145).
Upgrades Dart DevTools to version 2.28.3 (issue #54085).
v3.2.0
Compare Source
Language
Dart 3.2 adds the following features. To use them, set your package's SDK
constraint lower bound to 3.2 or greater (
sdk: '^3.2.0'
).Private field promotion: In most circumstances, the types of private final
fields can now be promoted by null checks and
is
tests. For example:To ensure soundness, a field is not eligible for field promotion in the
following circumstances:
test and the usage, invalidating the promotion).
non-final field (because an access to an overridden field might resolve at
runtime to the overriding getter or field).
elsewhere in the program).
other unrelated class in the library (because a class elsewhere in the
program might extend one of the classes and implement the other, creating an
override relationship between them).
C
in the library whose interface contains agetter with the same name, but
C
does not have an implementation of thatgetter (such unimplemented getters aren't safe for field promotion, because
they are implicitly forwarded to
noSuchMethod
, which might not return thesame value each time it's called).
Breaking Change #53167: Use a more precise split point for refutable
patterns. Previously, in an if-case statement, if flow analysis could prove
that the scrutinee expression was guaranteed to throw an exception, it would
sometimes fail to propagate type promotions implied by the pattern to the
(dead) code that follows. This change makes the type promotion behavior of
if-case statements consistent regardless of whether the scrutinee expression
throws an exception.
No live code is affected by this change, but there is a small chance that the
change in types will cause a compile-time error to appear in some dead code in
the user's project, where no compile-time error appeared previously.
Libraries
dart:async
broadcast
parameter toStream.empty
constructor.dart:cli
waitFor
is disabled by default and slated for removal in 3.4. Attemptingto call this function will now throw an exception. Users that still depend
on
waitFor
can enable it by passing--enable_deprecated_wait_for
flagto the VM.
dart:convert
utf8.encode()
andUtf8Codec.encode()
fromList<int>
toUint8List
.dart:developer
Service.getIsolateID
method.getIsolateId
method toService
.getObjectId
method toService
.dart:ffi
NativeCallable.isolateLocal
constructor. This createsNativeCallable
s with the same functionality asPointer.fromFunction
,except that
NativeCallable
accepts closures.NativeCallable.keepIsolateAlive
method, which determines whetherthe
NativeCallable
keeps the isolate that created it alive.NativeCallable
constructors can now accept closures. PreviouslyNativeCallable
s had the same restrictions asPointer.fromFunction
, andcould only create callbacks for static functions.
NativeCallable.nativeFunction
now throws anerror if is called after the
NativeCallable
has already beenclose
d. Callsto
close
after the first are now ignored.dart:io
Breaking change #53005: The headers returned by
HttpClientResponse.headers
andHttpRequest.headers
no longer includetrailing whitespace in their values.
Breaking change #53227: Folded headers values returned by
HttpClientResponse.headers
andHttpRequest.headers
now have a spaceinserted at the fold point.
dart:isolate
Isolate.packageConfigSync
andIsolate.resolvePackageUriSync
APIs.dart:js_interop
JSNumber.toDart
is removed in favor oftoDartDouble
andtoDartInt
tomake the type explicit.
Object.toJS
is also removed in favor ofObject.toJSBox
. Previously, this function would allow Dart objects to flowinto JS unwrapped on the JS backends. Now, there's an explicit wrapper that is
added and unwrapped via
JSBoxedDartObject.toDart
. Similarly,JSExportedDartObject
is renamed toJSBoxedDartObject
and the extensionsObjectToJSExportedDartObject
andJSExportedDartObjectToObject
are renamedto
ObjectToJSBoxedDartObject
andJSBoxedDartObjectToObject
in order toavoid confusion with
@JSExport
.Type parameters must now be bound to a static interop type or one of the
dart:js_interop
types likeJSNumber
when used in an external API. Thisonly affects
dart:js_interop
classes and notpackage:js
or other forms ofJS interop.
dart:js_interop
types:@staticInterop
types can subtype onlyJSObject
andJSAny
from the set ofJS types in
dart:js_interop
. Subtyping other types fromdart:js_interop
would result in confusing type errors before, so this makes it a static error.
dart:js_interop
and@staticInterop
APIs:Static interop APIs will now use the same global context as non-static interop
instead of
globalThis
to avoid a greater migration. Static interop APIs,either through
dart:js_interop
or the@staticInterop
annotation, have usedJavaScript's
globalThis
as the global context. This is relevant to thingslike external top-level members or external constructors, as this is the root
context we expect those members to reside in. Historically, this was not the
case in dart2js and DDC. We used either
self
or DDC'sglobal
in non-staticinterop APIs with
package:js
. So, static interop APIs will now use one ofthose global contexts. Functionally, this should matter in only a very small
number of cases, like when using older browser versions.
dart:js_interop
'sglobalJSObject
is also renamed toglobalContext
and returns the globalcontext used in the lowerings.
dart:js_interop
External APIs:External JS interop APIs when using
dart:js_interop
are restricted to a setof allowed types. Namely, this includes the primitive types like
String
, JStypes from
dart:js_interop
, and other static interop types (either through@staticInterop
or extension types).dart:js_interop
isNull
andisUndefined
:null
andundefined
can only be discerned in the JS backends. dart2wasmconflates the two values and treats them both as Dart null. Therefore, these
two helper methods should not be used on dart2wasm and will throw to avoid
potentially erroneous code.
dart:js_interop
typeofEquals
andinstanceof
:Both APIs now return a
bool
instead of aJSBoolean
.typeofEquals
alsonow takes in a
String
instead of aJSString
.dart:js_interop
JSAny
andJSObject
:These types can only be implemented, and no longer extended, by user
@staticInterop
types.dart:js_interop
JSArray.withLength
:This API now takes in an
int
instead ofJSNumber
.Tools
Development JavaScript compiler (DDC)
JavaScript Object prototype.
JavaScript
Symbol
s andBigInt
s are now associated with their owninterceptor and should not be used with
package:js
classes. These types werebeing intercepted with the assumption that they are a subtype of JavaScript's
Object
, but this is incorrect. This lead to erroneous behavior when usingthese types as Dart
Object
s. See #53106 for more details. Usedart:js_interop
'sJSSymbol
andJSBigInt
with extension types to interopwith these types.
Production JavaScript compiler (dart2js)
JavaScript
Symbol
s andBigInt
s are now associated with their owninterceptor and should not be used with
package:js
classes. These types werebeing intercepted with the assumption that they are a subtype of JavaScript's
Object
, but this is incorrect. This lead to erroneous behavior when usingthese types as Dart
Object
s. See #53106 for more details. Usedart:js_interop
'sJSSymbol
andJSBigInt
with extension types to interopwith these types.
Dart command line
dart create
command has a newcli
templateto quickly create Dart command-line applications
with basic argument parsing capabilities.
To learn more about using the template,
run
dart help create
.Dart format
--enable-experiment
command-line option to enable languageexperiments.
DevTools
2.28.1 releases of DevTools.
Linter
annotate_redeclares
][annotate_redeclares] lint.use_build_context_synchronously
][use_build_context_synchronously] lint as stable.Pub
dart pub upgrade --tighten
which will update dependencies' lowerbounds in
pubspec.yaml
to match the current version.dart pub get
/add
/upgrade
will now show if a dependencychanged between direct, dev and transitive dependency.
dart pub upgrade
no longer shows unchanged dependencies.v3.1.5
Compare Source
This is a patch release that:
change in Node.js 21 affected the Dart Web compiler runtime. This patch
release accommodates for those changes (issue #53810).
v3.1.4
Compare Source
This is a patch release that:
value of variables while debugging code (issue [#53747]).
v3.1.3
Compare Source
This is a patch release that:
Fixes a bug in dart2js which would cause the compiler to crash when using
@staticInterop
@anonymous
factory constructors with type parameters (seeissue #53579 for more details).
The standalone Dart VM now exports symbols only for the Dart_* embedding API
functions, avoiding conflicts with other DSOs loaded into the same process,
such as shared libraries loaded through
dart:ffi
, that may have differentversions of the same symbols (issue [#53503]).
Fixes an issue with super slow access to variables while debugging.
The fix avoids searching static functions in the imported libraries
as references to members are fully resolved by the front-end. (issue
#53541)
v3.1.2
Compare Source
This is a patch release that:
Fixes a bug in dart2js which crashed the compiler when a typed record pattern
was used outside the scope of a function body, such as in a field initializer.
For example
final x = { for (var (int a,) in someList) a: a };
(issue #53449)
Fixes an expedient issue of users seeing an unhandled
exception pause in the debugger, please https://github.com/dart-lang/sdk/issues/53450es/53450 for more
details.
The fix uses try/catch in lookupAddresses instead of
Future error so that we don't see an unhandled exception
pause in the debugger (issue #53450)
v3.1.1
Compare Source
This is a patch release that:
nested record pattern, where the nested record pattern uses record
destructuring shorthand syntax, for example
final ((:a, :b), c) = record;
(issue #53352).
v3.1.0
Compare Source
Libraries
dart:async
interface
modifier to purely abstract classes:MultiStreamController
,StreamConsumer
,StreamIterator
andStreamTransformer
. As a result, these types can only be implemented,not extended or mixed in.
dart:core
Uri.base
on native platforms now respectsIOOverrides
overridingcurrent directory (#39796).
dart:ffi
NativeCallable
class, which can be used to create callbacks thatallow native code to call into Dart code from any thread. See
NativeCallable.listener
. In future releases,NativeCallable
will beupdated with more functionality, and will become the recommended way of
creating native callbacks for all use cases, replacing
Pointer.fromFunction
.dart:io
sameSite
to theCookie
class.SameSite
.FileSystemEvent
issealed
. This meansthat
FileSystemEvent
cannot be extended or implemented.Platform
is instantiated.Platform.lineTerminator
which exposes the character or charactersthat the operating system uses to separate lines of text, e.g.,
"\r\n"
on Windows.dart:js_interop
ObjectLiteral
is removed fromdart:js_interop
. It's no longer needed inorder to declare an object literal constructor with inline classes. As long as
an external constructor has at least one named parameter, it'll be treated as
an object literal constructor. If you want to create an object literal with no
named members, use
{}.jsify()
.Other libraries
package:js
@staticInterop
andexternal
extension members:external
@staticInterop
members andexternal
extension members can nolonger be used as tear-offs. Declare a closure or a non-
external
method thatcalls these members, and use that instead.
@staticInterop
andexternal
extension members:external
@staticInterop
members andexternal
extension members willgenerate slightly different JS code for methods that have optional parameters.
Whereas before, the JS code passed in the default value for missing optionals,
it will now pass in only the provided members. This aligns with how JS
parameters work, where omitted parameters are actually omitted. For example,
calling
external void foo([int a, int b])
asfoo(0)
will now result infoo(0)
, and notfoo(0, null)
.Tools
DevTools
releases of DevTools.
Linter
your package's
analysis_options.yaml
file:no_self_assignments
no_wildcard_variable_uses
v3.0.7
Compare Source
This is a patch release that:
bad codegen causing a
TypeError
orNoSuchMethodError
to be thrownat runtime (issue #53001).
v3.0.6
Compare Source
This is a patch release that:
assignments (issue #52767).
is
oras
expressions involving record types with named fields (issue #52869).v3.0.5
Compare Source
This is a patch release that:
ListFactorySpecializer
during Flutter web builds (issue #52403).v3.0.4
Compare Source
This is a patch release that:
dart format
now handles formatting nullable record typeswith no fields (dart_style issue #1224).
(issue #52480).
v3.0.3
Compare Source
This is a patch release that:
returning an unboxed record (issue #52449).
or-pattern might be erroneously reported as being mismatched (issue #52373).
interface
modifiers on the purely abstract classesMultiStreamController
,StreamConsumer
,StreamIterator
andStreamTransformer
(issue #52334).InternetAddress.tryParse
isused (issue #52423).
a pattern match using a variable or wildcard pattern with a nullable
record type (issue #52439).
cache on Windows (issue #52386).
v3.0.2
Compare Source
This is a patch release that:
the fields don't match the cases (issue #52438).
generated with
dart doc
(issue #3392).leading to higher memory usage (issue #52352).
(issue: #52078).
v3.0.1
Compare Source
This is a patch release that:
(issue #124369).
and records (issue #51899).
void
in a switch case expression(issue #52191).
refers to a private getter (issue #52041).
when
andas
as variable names in patterns(issue #52260).
(issue #52241).
v3.0.0
Compare Source
Language
Dart 3.0 adds the following features. To use them, set your package's SDK
constraint lower bound to 3.0 or greater (
sdk: '^3.0.0'
).[Records]: Records are anonymous immutable data structures that let you
aggregate multiple values together, similar to [tuples][] in other languages.
With records, you can return multiple values from a function, create composite
map keys, or use them any other place where you want to bundle a couple of
objects together.
For example, using a record to return two values:
[Pattern matching]: Expressions build values out of smaller pieces.
Conversely, patterns are an expressive tool for decomposing values back into
their constituent parts. Patterns can call getters on an object, access
elements from a list, pull fields out of a record, etc. For example, we can
destructure the record from the previous example like so:
Patterns can also be used in [switch cases]. There, you can destructure values
and also test them to see if they have a certain type or value:
Also, as you can see, non-empty switch cases no longer need
break;
statements.
Breaking change: Dart 3.0 interprets [switch cases] as patterns instead of
constant expressions. Most constant expressions found in switch cases are
valid patterns with the same meaning (named constants, literals, etc.). You
may need to tweak a few constant expressions to make them valid. This only
affects libraries that have upgraded to language version 3.0.
[Switch expressions]: Switch expressions allow you to use patterns and
multi-way branching in contexts where a statement isn't allowed:
[If-case statements and elements]: A new if construct that matches a value
against a pattern and executes the then or else branch depending on whether
the pattern matches:
There is also a corresponding [if-case element] that can be used in collection
literals.
[Sealed classes]: When you mark a type
sealed
, the compiler ensures thatswitches on values of that type [exhaustively cover] every subtype. This
enables you to program in an [algebraic datatype][] style with the
compile-time safety you expect:
In this last example, the compiler reports an error that the switch doesn't
cover the subclass
Dusty
.[Class modifiers]: New modifiers
final
,interface
,base
, andmixin
on
class
andmixin
declarations let you control how the type can be used.By default, Dart is flexible in that a single class declaration can be used as
an interface, a superclass, or even a mixin. This flexibility can make it
harder to evolve an API over time without breaking users. We mostly keep the
current flexible defaults, but these new modifiers give you finer-grained
control over how the type can be used.
Breaking change: Class declarations from libraries that have been upgraded
to Dart 3.0 can no longer be used as mixins by default. If you want the class
to be usable as both a class and a mixin, mark it [
mixin class
][mixinclass]. If you want it to be used only as a mixin, make it a
mixin
declaration. If you haven't upgraded a class to Dart 3.0, you can still use it
as a mixin.
Breaking change [#50902][]: Dart reports a compile-time error if a
continue
statement targets a [label] that is not a loop (for
,do
andwhile
statements) or aswitch
member. Fix this by changing thecontinue
to target a valid labeled statement.
*Breaking change
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.