dart-sdk/pkg
Robert Nystrom 56eaffb392 [flip-patterns] Enable "records" and "patterns" experiment flags.
This turns on the flags for these two language features and makes
them generally accessible.

Doing so causes a number of tests to fail, but the failures are
approved and there are filed issues for them. Most of the
failures are minor or only affect code using the new language
features.

This CL:

- Enables the features in experimental_features.yaml.
- Re-generates all of the various files generated from that.
- Makes some analyzer and front end changes that this CL
  inherited from Paul's original CL flipping all of the 3.0
  feature flags. I don't know what these changes are about, but
  I assume they are necessary.
- Pins a couple of tests to 2.19 since they deliberately test
  behavior that is specific to 2.19. (For most test changes, I've
  landed them separately, but there are a couple of stragglers
  in this CL.)

This doesn't enable "class-modifiers" or "sealed-types" and doesn't
include the core lib changes related to those.

TEST=On bots

Change-Id: Id387753772286a958e20a3589a6e983995f2e4a6
Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/286344
Auto-Submit: Bob Nystrom <rnystrom@google.com>
Reviewed-by: Alexander Markov <alexmarkov@google.com>
Commit-Queue: Bob Nystrom <rnystrom@google.com>
Reviewed-by: Jake Macdonald <jakemac@google.com>
Reviewed-by: Nate Bosch <nbosch@google.com>
Reviewed-by: Johnni Winther <johnniwinther@google.com>
2023-03-10 20:02:23 +00:00
..
_fe_analyzer_shared [flip-patterns] Enable "records" and "patterns" experiment flags. 2023-03-10 20:02:23 +00:00
_js_interop_checks [kernel] Add VariableDeclaration.isSynthesized 2023-03-10 11:13:36 +00:00
analysis_server [flip-patterns] Enable "records" and "patterns" experiment flags. 2023-03-10 20:02:23 +00:00
analysis_server_client
analyzer [flip-patterns] Enable "records" and "patterns" experiment flags. 2023-03-10 20:02:23 +00:00
analyzer_cli
analyzer_plugin [flip-patterns] Enable "records" and "patterns" experiment flags. 2023-03-10 20:02:23 +00:00
analyzer_utilities
async_helper
build_integration
compiler [kernel] Add VariableDeclaration.isSynthesized 2023-03-10 11:13:36 +00:00
dart2js_info
dart2js_runtime_metrics
dart2js_tools
dart2native
dart2wasm [kernel] Add VariableDeclaration.isSynthesized 2023-03-10 11:13:36 +00:00
dart_internal
dartdev [ Observatory ] Disable serving Observatory by default 2023-03-10 16:01:41 +00:00
dds
dds_service_extensions
dev_compiler [kernel] Add VariableDeclaration.isSynthesized 2023-03-10 11:13:36 +00:00
expect
front_end [flip-patterns] Enable "records" and "patterns" experiment flags. 2023-03-10 20:02:23 +00:00
frontend_server
js
js_ast
js_runtime
js_shared
kernel [kernel] Add VariableDeclaration.isSynthesized 2023-03-10 11:13:36 +00:00
language_versioning_2_7_test
meta
mmap
modular_test
native_stack_traces
nnbd_migration
scrape
smith
sourcemap_testing
status_file
telemetry
test_runner
testing
vm [kernel] Add VariableDeclaration.isSynthesized 2023-03-10 11:13:36 +00:00
vm_service
vm_snapshot_analysis
wasm_builder
.gitignore
analysis_options.yaml
BUILD.gn
OWNERS
pkg.dart
pkg.status
README.md

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