commit | e5244c88c91e03f4e311d0ddf5b21eb70f20c093 | [log] [tgz] |
---|---|---|
author | Paul Berry <paulberry@google.com> | Wed Jan 17 23:57:13 2024 +0000 |
committer | Commit Queue <dart-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Jan 17 23:57:13 2024 +0000 |
tree | e15485edd4825efbffd47ac86cac9941aa5fb03e | |
parent | 909f02415016b796e3367bbe96fe2a25b8cd18b2 [diff] |
[beta] Fix handling of extension types in relational patterns. In https://dart-review.googlesource.com/c/sdk/+/345082, type erasure was added to the handling of relational patterns, to address some co19 failures, e.g.: extension type const BoolET1(bool _) {} const True1 = BoolET1(true); String testStatement1(bool b) { switch (b) { case == True1: ... } } This was failing because the type of `True1` (`BoolET1`) is not assignable to the argument type of `operator==`, which is `Object`. (This is because extension types do not, by default, extend `Object`; they extend `Object?`). Adding type erasure elimited the co19 failure, but it caused other code to be allowed that shouldn't be allowed, such as: extension type const E(int representation) implements Object {} class A { bool operator <(int other) => ...; } const E0 = E(0); test(A a) { if (a case < E0) ...; } This shouldn't be allowed because the type expected by `A.<` is `int`; allowing `E0` to be passed to this operator breaks extension type encapsulation. The correct fix is for assignability checks for `operator==` to use `S?` rather than `S`, where `S` is the argument type of `operator==`. This is consistent with the patterns specification, and it ensures that `== null` and `!= null` are allowed, while continuing to prohibit relational patterns that break extension type encapsulation. Fixes https://github.com/dart-lang/sdk/issues/54594. Bug: https://github.com/dart-lang/sdk/issues/54594. Change-Id: Id1f7a52f75e91c0b3b3d535aab68d38da68d37a5 Cherry-pick: https://dart-review.googlesource.com/c/sdk/+/345860 Cherry-pick-request: https://github.com/dart-lang/sdk/issues/54612 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/345826 Reviewed-by: Chloe Stefantsova <cstefantsova@google.com> Commit-Queue: Paul Berry <paulberry@google.com> Reviewed-by: Konstantin Shcheglov <scheglov@google.com>
Dart is:
Approachable: Develop with a strongly typed programming language that is consistent, concise, and offers modern language features like null safety and patterns.
Portable: Compile to ARM, x64, or RISC-V machine code for mobile, desktop, and backend. Compile to JavaScript or WebAssembly for the web.
Productive: Make changes iteratively: use hot reload to see the result instantly in your running app. Diagnose app issues using DevTools.
Dart's flexible compiler technology lets you run Dart code in different ways, depending on your target platform and goals:
Dart Native: For programs targeting devices (mobile, desktop, server, and more), Dart Native includes both a Dart VM with JIT (just-in-time) compilation and an AOT (ahead-of-time) compiler for producing machine code.
Dart Web: For programs targeting the web, Dart Web includes both a development time compiler (dartdevc) and a production time compiler (dart2js).
Dart is free and open source.
See LICENSE and PATENT_GRANT.
Visit dart.dev to learn more about the language, tools, and to find codelabs.
Browse pub.dev for more packages and libraries contributed by the community and the Dart team.
Our API reference documentation is published at api.dart.dev, based on the stable release. (We also publish docs from our beta and dev channels, as well as from the primary development branch).
If you want to build Dart yourself, here is a guide to getting the source, preparing your machine to build the SDK, and building.
There are more documents on our wiki.
The easiest way to contribute to Dart is to file issues.
You can also contribute patches, as described in Contributing.