commit | deebb52c2b229c9606408b8edc51f83de1cbee31 | [log] [tgz] |
---|---|---|
author | Paul Berry <paulberry@google.com> | Tue Nov 21 00:32:19 2023 +0000 |
committer | Commit Queue <dart-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Nov 21 00:32:19 2023 +0000 |
tree | 2b227adb920a10c4df513d081ac1516da527c6f0 | |
parent | 93e7fd5a0e44e3aae34b97b3599d1b9b0e75f300 [diff] |
Add support for null shorting expressions to the Wolf analysis prototype. The AST-to-IR conversion stage now handles null-shorting property accesses (both for reads and writes). This required adding the following instruction types: `eq`, `block`, and `brIf`. In order to make `eq` easier to test, support was also added for AST-to-IR conversion of testing binary expressions using `==`. The way null shorting is encoded in the IR is by issuing a `block` instruction when null shorting starts, and an `end` instruction when it terminates. Anywhere a null check appears within the null shorting expression, the null check uses a `brIf(0)` instruction to branch to the `end` in the case a `null` is found. To make it easier to keep track of when `block` and `end` instructions need to be generated, `RawIRWriter` keeps track of a count of the current nesting of control flow contsructs. In order for the interpreter to find to the appropriate `end` instruction when a branch is taken, a new scope analyzer is added. Later CLs will expand on it and use it for static analysis as well. Change-Id: I09ca34eaa900d47f7a4014cbc8db2a48a1d69e1e Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/336800 Reviewed-by: Phil Quitslund <pquitslund@google.com> Commit-Queue: Paul Berry <paulberry@google.com>
Dart is:
Optimized for UI: Develop with a programming language specialized around the needs of user interface creation.
Productive: Make changes iteratively: use hot reload to see the result instantly in your running app.
Fast on all platforms: Compile to ARM & x64 machine code for mobile, desktop, and backend. Or compile to JavaScript for the web.
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.