| commit | ac6d86c7378cbc708f785bd83932053b81749bfa | [log] [tgz] |
|---|---|---|
| author | Paul Berry <paulberry@google.com> | Tue Nov 19 17:17:18 2024 +0000 |
| committer | Commit Queue <dart-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Nov 19 17:17:18 2024 +0000 |
| tree | 5f06b61dd34a2f65e4653ce10580a31f664e0989 | |
| parent | d79fcdf4cd08a699d9ac4426962b19b4b5aef25a [diff] |
[analyzer] Represent `Null` as `NullTypeImpl`. This change introduces the class `NullTypeImpl` to represent the special type `Null`, which was previously represented as an ordinary `InterfaceType`. This class mirrors the CFE's `NullType` class. Adding it will facilitate further code sharing between the analyzer and the CFE, because it will allow code that's shared between the analyzer and CFE to use `is` tests to recognize the type `Null`. The new `NullTypeImpl` class always has a nullability suffix of `NullabilitySuffix.none`, so it is impossible for the type `Null?` to occur. This is a benign behavioral change; previously there were some circumstances in which the type `Null?` might occur in the analyzer, but the type `Null?` behaved the same as `Null` so there was no user-visible effect. This behavioral change brings the analyzer's treatment of `Null` into alignment with that of the CFE. This is the first step in a planned patch series. In follow-up CLs, I intend to: - Introduce a public-facing `NullType` for use by clients. - Change `NullTypeImpl` so that it no longer extends `InterfaceTypeImpl`. - Add a base class that is common to the analyzer and CFE `NullType` representations. Change-Id: I9cea84d8149347bffdee006d544af28c66eba429 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/396320 Commit-Queue: Paul Berry <paulberry@google.com> Reviewed-by: Konstantin Shcheglov <scheglov@google.com> Reviewed-by: Brian Wilkerson <brianwilkerson@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 in our repo at docs.
The easiest way to contribute to Dart is to file issues.
You can also contribute patches, as described in Contributing.
Future plans for Dart are included in the combined Dart and Flutter roadmap on the Flutter wiki.