dart-sdk/pkg
Paul Berry 3fdc3c2588 Integrate shared type analysis of switch statements with analyzer.
This change replaces ResolverVisitor.visitSwitchStatement
with a call to the new shared type analyzer, and implements the
necessary callbacks to allow analysis to work end-to-end.

Additionally, it changes the convention context types in resolver
methods so that UnknownInferredType is now consistently used to
represent the unknown type (`?`).  Previously `null` was sometimes
used instead.

Change-Id: Idb81a7dc888dfbf460c78b93a99367c0c9263610
Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/256960
Reviewed-by: Brian Wilkerson <brianwilkerson@google.com>
Commit-Queue: Paul Berry <paulberry@google.com>
Reviewed-by: Konstantin Shcheglov <scheglov@google.com>
2022-09-21 23:00:20 +00:00
..
_fe_analyzer_shared Shared type analysis for patterns: rename finishStatementCase 2022-09-20 20:37:09 +00:00
_js_interop_checks [pkg:js] Add proto argument to createStaticInteropMock 2022-09-16 20:13:30 +00:00
analysis_server Report EXPECTED_NAMED_TYPE_X when not a NamedType is parsed. 2022-09-21 02:24:45 +00:00
analysis_server_client Fix typos 2022-09-16 19:35:00 +00:00
analyzer Integrate shared type analysis of switch statements with analyzer. 2022-09-21 23:00:20 +00:00
analyzer_cli
analyzer_plugin [analyzer] use preferred quote-style when generating imports 2022-09-21 17:12:46 +00:00
analyzer_utilities Fix typos 2022-09-16 19:35:00 +00:00
async_helper
build_integration
compiler [dart2js] Migrate interceptor_data.dart to null safety. 2022-09-21 19:56:01 +00:00
dart2js_info
dart2js_runtime_metrics
dart2js_tools
dart2native [pkg/dart2native] Refactor MachO parsing. 2022-09-07 11:32:37 +00:00
dart2wasm [dart2wasm] Skip selectors with no implementations in dispatch table 2022-09-21 09:56:36 +00:00
dart_internal
dartdev Remove emoji from null safety terminal messages. They are not rendering correctly on Windows. 2022-09-15 16:41:29 +00:00
dds [ DDS ] Fix IsolateManager.initialize() not correctly handling Sentinel responses 2022-09-20 18:51:05 +00:00
dds_service_extensions
dev_compiler Revert "[ddc] Add non-null assertions when setting fields" 2022-09-20 17:19:38 +00:00
expect
front_end [cfe] Handle structurally constant record literals 2022-09-21 14:19:16 +00:00
frontend_server [frontend_server] Migrate frontend_server_starter 2022-09-16 08:06:49 +00:00
js
js_ast
js_runtime
js_shared
kernel [cfe] Implement RecordLiteral.transformOrRemoveChildren 2022-09-21 08:49:16 +00:00
language_versioning_2_7_test
meta
modular_test
native_stack_traces
nnbd_migration Migration: properly handle a field overriding a field in a mixin. 2022-09-19 17:11:51 +00:00
scrape
smith
sourcemap_testing
status_file
telemetry
test_runner [analyzer] fix diagnostics for lints map 2022-09-20 17:11:35 +00:00
testing
vm [vm/aot] Initial support for records in TFA 2022-09-16 18:43:50 +00:00
vm_service [pkg/vm_service] turn on a few more lints for this package 2022-09-19 17:02:14 +00:00
vm_snapshot_analysis
wasm_builder [dart2wasm] Fix memory definition. 2022-09-06 18:25:36 +00:00
.gitignore
BUILD.gn
OWNERS
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