Fine. Add RequirementsManifestDigest; stop caching linked bundles

Introduce a compact digest for requirements validation and remove the
process-wide in-memory cache of linked bundles. This reduces heap usage
and speeds the common "no-op" validation path without sacrificing
correctness.

What’s new
- Add `RequirementsManifestDigest`: a compact map from library `Uri` to
  `LibraryManifest.hashForRequirements`. It supports binary read/write and a
  fast `isSatisfied(LinkedElementFactory)` check.
- Add `RequirementsManifest.toDigest()` to build the digest directly from a
  manifest, including re-exported libraries.

Linking & caching changes
- Replace `LinkedBundleProvider` with a simple on-disk cache entry:
  `_LinkedBundleCacheEntry { nonTransitiveApiSignature, requirementsDigest,
  requirementsBytes, libraryManifests, linkedBytes }`.
- Persist both the digest (for fast checks) and the raw requirements bytes
  (to lazily deserialize for a full check only when needed).
- In `LibraryContext`, add `_probeLinkedBundle(...)`:
  - If fine-grained deps are off, any cache hit is reused (key already
    includes the transitive API signature).
  - If on, verify `nonTransitiveApiSignature`, then try the digest fast path.
    If the digest fails, fall back to `requirements.isSatisfied(...)`.
- Write/read cache entries directly to/from `ByteStore`; do not maintain an
  in-memory map of previously deserialized bundles.

Wiring cleanup
- Remove `LinkedBundleProvider` from `AnalysisContextCollectionImpl`,
  `ContextBuilderImpl`, `AnalysisDriver`, `LibraryContext`, and the micro
  resolver; adjust constructors and call sites accordingly.
- Drop state-printer output related to the removed provider.

Format bump
- Increment `AnalysisDriver.DATA_VERSION` to 567 to invalidate old cache
  data and reflect the new on-disk bundle format.

Why
- The prior in-memory provider retained requirements/manifests/linked bytes
  for many cycles, inflating heap in large workspaces and transitive edits.
- The digest enables a cheap, order-independent equality check that avoids
  deserializing `RequirementsManifest` in the overwhelmingly common case
  where nothing relevant changed.

Impact
- Lower peak memory (no process-wide bundle cache).
- Faster typical validation (digest check), with full checks only when
  hashes disagree or a library is missing.

Change-Id: I61d21cdffaa0b8e6ee1f87d0469c27b890061935
Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/451960
Commit-Queue: Konstantin Shcheglov <scheglov@google.com>
Reviewed-by: Johnni Winther <johnniwinther@google.com>
8 files changed
tree: f58222434569b777874ee701b65d9f05e09a81f7
  1. .dart_tool/
  2. .github/
  3. benchmarks/
  4. build/
  5. docs/
  6. pkg/
  7. runtime/
  8. samples/
  9. sdk/
  10. tests/
  11. third_party/
  12. tools/
  13. utils/
  14. .clang-format
  15. .gitattributes
  16. .gitconfig
  17. .gitignore
  18. .gn
  19. .mailmap
  20. .style.yapf
  21. AUTHORS
  22. BUILD.gn
  23. CHANGELOG.md
  24. codereview.settings
  25. CONTRIBUTING.md
  26. DEPS
  27. LICENSE
  28. OWNERS
  29. PATENT_GRANT
  30. PRESUBMIT.py
  31. pubspec.yaml
  32. README.dart-sdk
  33. README.md
  34. sdk.code-workspace
  35. sdk_args.gni
  36. sdk_packages.yaml
  37. SECURITY.md
  38. WATCHLISTS
README.md

Dart

An approachable, portable, and productive language for high-quality apps on any platform

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 platforms illustration

License & patents

Dart is free and open source.

See LICENSE and PATENT_GRANT.

Using Dart

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).

Building Dart

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.

Contributing to Dart

The easiest way to contribute to Dart is to file issues.

You can also contribute patches, as described in Contributing.

Roadmap

Future plans for Dart are included in the combined Dart and Flutter roadmap on the Flutter wiki.