Paul Berry
ea768b29a4
Renames `pkg/analyzer/lib/src/diagnostic/diagnostic.dart` to `pkg/analyzer/lib/src/diagnostic/diagnostic_message.dart`. The new name aligns better with the library's purpose (which is solely to export the class `DiagnosticMessageImpl` from `package:_fe_analyzer_shared`). This frees up the filename `pkg/analyzer/lib/src/diagnostic/diagnostic.dart` to be used as the repository for all generated analyzer messages. Change-Id: I6a6a6964be0904a383334974f1e64a03c0df551b Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/458381 Reviewed-by: Samuel Rawlins <srawlins@google.com> Reviewed-by: Konstantin Shcheglov <scheglov@google.com> Commit-Queue: Paul Berry <paulberry@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.