Sam Rawlins
903d77cc82
Work towards https://github.com/dart-lang/sdk/issues/60635 I tried to keep this minimal but still sensible: * Rename AnalysisErrorListener and all subtypes to use 'Diagnostic'. * Rename all instantiations of such classes if they previously contained the word 'error'. * Rename `RecordingDiagnosticListener.errors` to `.diagnostics`. * Rename some _testing_ instance members that had the word 'error' to instead use 'diagnostic'. Change-Id: I3948e27ba28ac2494092e04f4e1d201a20cc1135 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/433004 Commit-Queue: Samuel Rawlins <srawlins@google.com> Reviewed-by: Paul Berry <paulberry@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.