Konstantin Shcheglov
291d8ae07d
Create `TypeParameterElementImpl` instances when their owning elements are constructed, instead of materializing them later in builders, fragment linkers, and bundle reading. This makes ownership explicit in the element model. Update synthetic executable construction in inheritance handling to build fresh type parameter and formal parameter elements. Top-merge and covariance inheritance were previously able to reuse fragments from other executables, which could attach fragments to the wrong element and produce invalid synthetic members for generic signatures. For type aliases, serialize the first fragment directly instead of a fragment list. This matches how type alias elements are constructed and avoids a separate read-time step that recreated type parameter elements. Bump the data version for the format change. Change-Id: If4f203f65fb11bcd0ffd1dcc0e47956b9fb2597b Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/496780 Commit-Queue: Konstantin Shcheglov <scheglov@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>.