commit 3f749efdd0b512ebbce2a798f6a18fcf8dc5489b
author Konstantin Shcheglov <scheglov@google.com> Mon Sep 29 10:47:47 2025 -0700
committer Commit Queue <dart-scoped@luci-project-accounts.iam.gserviceaccount.com> Mon Sep 29 10:47:47 2025 -0700
tree 70476ae712e3a86759a0aaa5e32863dab5666b8a
parent 2e75a5498d62b17168538e8e7d6da3371ebd4426

Fine. Use manifest hash to fast-path export validation

Add a fast path for validating `export` requirements by recording and
comparing the exported library’s `LibraryManifest.hashForRequirements`.

Previously, `ExportRequirement.isSatisfied` walked the exported
namespace and compared each expected ID, even when the exported
library’s manifest had not changed. This patch short-circuits that work
when the manifest hash matches the recorded value.

Key changes:
- ExportRequirement now includes a snapshot of the exported library’s
  `hashForRequirements` and serializes it.
- `isSatisfied()` returns success immediately when the current manifest
  hash equals the recorded hash, skipping combinator and per-name ID
  checks. (Missing exported libraries still report a failure.)
- `LibraryExportRequirements.build()` captures the hash from the
  exported library’s manifest and stores it in each requirement.
- Bump `AnalysisDriver.DATA_VERSION` from 565 to 566 due to the binary
  format change.

Impact:
- Avoids re-validating unchanged re-exports, reducing unnecessary work
  in incremental analyses.
- Maintains correctness because the hash covers exactly the
  requirement-visible state used by validation.

Change-Id: I2ecaabe45be7326ed11257a13d04a55de79f328d
Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/451941
Reviewed-by: Paul Berry <paulberry@google.com>
Commit-Queue: Konstantin Shcheglov <scheglov@google.com>