| commit | 637777857f0843545d1a68f2b84e2a957895a59d | [log] [tgz] |
|---|---|---|
| author | Konstantin Shcheglov <scheglov@google.com> | Tue Sep 30 08:59:41 2025 -0700 |
| committer | Commit Queue <dart-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Sep 30 08:59:41 2025 -0700 |
| tree | d95a72aaa6dd0c0c4f76a577f2aadbe10f2ecf7e | |
| parent | cd26fe29fb639e6e6d1e36e3983a6fe5018d80e9 [diff] |
Fine. Use digest in diagnostics bundle; drop in-memory cache Introduce `RequirementsManifestDigest` to `LibraryDiagnosticsBundle` and remove the driver's in-memory diagnostics bundle cache. Bundles are now always read from the byte store; we first validate using the digest and only fall back to a full requirements check when needed. Key changes: - Replace stored `RequirementsManifest` with: - a compact `RequirementsManifestDigest` for fast validation, and - the full manifest serialized as raw bytes, decoded on demand. - Remove `_libraryDiagnosticsCache` and the API-signature validation path; reuse is governed by the digest + (rare) full check. - Persist bundles via `LibraryDiagnosticsBundle.write(...)`. - Bump `DATA_VERSION` to 569 to reflect the new on-disk layout. Impact: - Peak memory drops from 652 MB to 544 MB (−108 MB, −16.6%). - The fine-deps mode is now within +32 MB (+6.25%) of the 512 MB baseline without fine-grained dependencies. - Typical reuse gets a cheaper “is satisfied” check; full requirement deserialization is avoided on the common path. Compatibility: - The bundle format changed; older cached entries are invalidated by the data version bump. No public API behavior changes. Rationale: - Eliminates a large RAM resident cache while preserving fast re-use of diagnostics through a stable, order-independent digest. Change-Id: I3479ca13bc48922ecd8fa351dbe53a0e3390a29e Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/452224 Commit-Queue: Konstantin Shcheglov <scheglov@google.com> Reviewed-by: Johnni Winther <johnniwinther@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.