commit | e2fdf18b66ba7da09f60f9d91966a86d7e38f827 | [log] [tgz] |
---|---|---|
author | Stephen Adams <sra@google.com> | Tue May 27 12:47:44 2025 -0700 |
committer | Commit Queue <dart-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue May 27 12:47:44 2025 -0700 |
tree | a10e9635de5746b81d9d9cbec031ee61efa525c7 | |
parent | 89552236ffb3c60bd2bdcc8a1c68d3d5c441214f [diff] |
[dart2js] Refine types based on test with late sentinel A small number of getters for `late final` instance fields with initializers have better code. When the initializing expression provably does not write to the backing field*, the field value is re-used rather than re-loaded for the 'final' check (that the field has not been assigned during the evaluation of the initializer). We are testing both `value === $` and `value !== $`: ``` value = _this.___LayoutWidgetState_firstChild_FI; if (value === $) { result = A._LayoutWidgetState__buildChild(B.ValueKey_1, _this._widget.node.firstChild); value !== $ && A.throwUnnamedLateFieldADI(); _this.___LayoutWidgetState_firstChild_FI = result; value = result; } ``` In this change we refine the type of the tested value to late sentinel, allowing the check to be removed: ``` if (value === $) value = _this.___LayoutWidgetState_firstChild_FI = A._LayoutWidgetState__buildChild(B.ValueKey_1, _this._widget.node.firstChild); ``` *This effect analysis is pretty simple ('writes some field'), but if improved, we might expect more `late final` getters to benefit. Change-Id: I444ed157083663b848fb2f115d0575e544b47727 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/430962 Reviewed-by: Mayank Patke <fishythefish@google.com> Commit-Queue: Stephen Adams <sra@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.