Robert Nystrom
2ee771a4f6
I also cleaned up a bunch of places that referred to them. Change-Id: I45f68818c892f8620ea04257885ffa3763374bb5 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/335863 Auto-Submit: Bob Nystrom <rnystrom@google.com> Commit-Queue: Bob Nystrom <rnystrom@google.com> Reviewed-by: Alexander Thomas <athom@google.com>
29 lines
1.2 KiB
Markdown
29 lines
1.2 KiB
Markdown
# 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](https://github.com/dart-lang/sdk/blob/main/pkg/test_runner/lib/src/compiler_configuration.dart).
|
|
|
|
## 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.
|
|
|
|
[has been replaced]: https://github.com/dart-lang/sdk/issues/48457 |