Paul Berry
9bd89a769d
For some reason, when a `CheckSorted` presubmit invokes `verify_sorted_test.dart`, the `-r` flag is preventing the compiler from picking up the proper language version from `.dart_tool/package_config.json`. This is interfering with my ability to run presubmits for https://dart-review.googlesource.com/c/sdk/+/505046. See https://github.com/dart-lang/sdk/issues/63464 for additional details. As a temporary workaround, this CL removes the `-r` flag. It should be reverted once https://github.com/dart-lang/sdk/issues/63464 has been fixed (and the pre-built SDK has been updated to include the fix). Change-Id: Ibc48eec4ef382d6afe17d73454f07dcd6a6a6964 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/506700 Commit-Queue: Paul Berry <paulberry@google.com> Reviewed-by: Samuel Rawlins <srawlins@google.com> Reviewed-by: Konstantin Shcheglov <scheglov@google.com>
SDK development code analysis
dartanalyzer used to be the tool for statically analyzing dart code
at the command line. However, this tool has been replaced with
dart analyze for this purpose in current SDKs and will no longer
be published on pub.
Do not depend on the command line interface or other semantics in
this directory as it is now an internal tool for SDK development, used
as the dart2analyzer "compiler" for tools/test.py in the SDK.
It is configured as part of the test runner,
here.
SDK development usage
For SDK development, run analysis from the test tool to validate analysis conclusions on language samples in the testing directory. From the root of the SDK:
tools/test.py --build --use-sdk -c dart2analyzer co19 language
This will build the Dart VM and compile dartanalyzer into a snapshot, then use
that snapshot while analyzing those directories under testing/. Without
--use-sdk, test.py will use the source code version of the analyzer
instead of the compiled one, which can be useful for debugging.