| commit | 563cc890ae2421460b9e163392e778e40662ceef | [log] [tgz] |
|---|---|---|
| author | Konstantin Shcheglov <scheglov@google.com> | Fri Aug 29 13:49:11 2025 -0700 |
| committer | Commit Queue <dart-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Aug 29 13:49:11 2025 -0700 |
| tree | e7fd0a2b9a0cec3539ce2a57253023b002d85e0e | |
| parent | c0e9ac38f2be8ad71de12f3b3725bd30ac448b03 [diff] |
Fine. Optimize linked bundle reuse with an API signature shortcut When fine-grained dependencies are enabled, reusing a cached linked bundle requires validating that all its requirements are still satisfied. While cheaper than relinking, this validation is still not free. Many common code modifications, such as changing a function body, do not affect the transitive API signature of a library cycle. In such scenarios, if the bundle's requirements were already validated against this signature, they will remain valid. This change introduces an optimization to avoid redundant validation. The `LinkedBundleEntry` now caches the last transitive API signature for which it was successfully validated. If a request is made for a cycle with a matching signature, the expensive requirements check is skipped, and the bundle is reused directly. Additionally, the driver events related to bundle reuse have been refactored. Several "CannotReuse" events are consolidated into a single `CheckLinkedBundleRequirements` event, simplifying event tracking. Similar to https://dart-review.googlesource.com/c/sdk/+/447520 Change-Id: I2165bccf4fee5cd01963f0ca4b432919105b91a2 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/447820 Commit-Queue: Konstantin Shcheglov <scheglov@google.com> Reviewed-by: Paul Berry <paulberry@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.