Konstantin Shcheglov
3cc5f5669b
Capture the simply-boundedness of instance elements in the fine-grained manifest and stop baking `isValidMixin` into item IDs. What: - Add `isSimplyBounded` to `InstanceItem` and all subclasses (`ClassItem`, `EnumItem`, `ExtensionItem`, `ExtensionTypeItem`, `MixinItem`). Persist it in summaries and compare it in `match`. - Update the summary schema to write/read `isSimplyBounded` immediately after `typeParameters` for all instance items. - Reclassify `ClassElementImpl.isValidMixin` from `@trackedIncludedInId` to `@trackedIndirectly`. - Bump `AnalysisDriver.DATA_VERSION` from 533 to 536. Why: - `isSimplyBounded` is an observable property of generic declarations. Not recording it could allow identity reuse when simply-boundedness changes without other shape differences. Persisting it yields more precise matching and invalidation. - `isValidMixin` is derived from other fields (e.g., `supertype`, constructors). Tracking it indirectly avoids unnecessary ID churn and reduces over-invalidation while remaining responsive to the inputs it depends on. Impact: - More accurate fine-grained dependency tracking for generics. - Fewer spurious item-ID changes from mixin validity checks. - Existing caches are invalidated due to the data format bump; no public API changes. Change-Id: I2700b16add664a4fd127f492fb186c8e1f3635e9 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/448100 Commit-Queue: Konstantin Shcheglov <scheglov@google.com> Reviewed-by: Johnni Winther <johnniwinther@google.com> Reviewed-by: Paul Berry <paulberry@google.com>
Package validation
The packages in pkg/ are automatically validated on the LUCI CI bots. The
validation is largely done by the tools/package_deps package; it can be tested
locally via:
dart tools/package_deps/bin/package_deps.dart
Packages which are published
There are several packages developed in pkg/ which are published to pub.
Validation of these packages is particularly important because the pub tools are
not used for these packages during development; we get our dependency versions
from the DEPS file. It's very easy for the dependencies specified in a package's
pubspec file to get out of date wrt the packages and versions actually used.
In order to better ensure we're publishing correct packages, we validate some properties of the pubspec files on our CI system. These validations include:
- that the dependencies listed in the pubspec are used in the package
- that all the packages used by the source are listed in the pubspec
- that we don't use relative path deps to pkg/ or third_party/ packages
Packages which are not published
For packages in pkg/ which we do not intend to be published, we put the following comment in the pubspec.yaml file:
# This package is not intended for consumption on pub.dev. DO NOT publish.
publish_to: none
These pubspecs are still validated by the package validation tool. The contents are more informational as the pubspecs for these packages are not consumed by the pub tool or ecosystem.
We validate:
- that the dependencies listed in the pubspec are used in the package
- that all the packages used by the source are listed in the pubspec
- that a reference to a pkg/ package is done via a relative path dependency
Adding new packages
Run gclient sync to re-generate .dart_tool/package_config.json after adding
a new package.
Testing packages
Currently dart test can't be used to run the tests, use test.py as usual.
E.g. the command ./tools/test.py -n...<path> runs all tests with prefix
<path>.