Files

T

Konstantin Shcheglov 3ab4358f33 Macro. Dispose AnalysisContextCollection(s) in analyzer_cli/

Change-Id: I0392f591c51c8eb1faef7b065ddfac18b1864e6a
Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/347201
Commit-Queue: Konstantin Shcheglov <scheglov@google.com>
Reviewed-by: Brian Wilkerson <brianwilkerson@google.com>

2024-01-19 00:05:17 +00:00

bin

…

lib

Macro. Dispose AnalysisContextCollection(s) in analyzer_cli/

2024-01-19 00:05:17 +00:00

test

add analysisOptions to FileResults

2024-01-18 22:05:18 +00:00

tool

analyzer: Move the Source class to be public API.

2023-11-14 17:10:37 +00:00

.gitignore

…

analysis_options.yaml

[pkg] remove duplicate config from the analysis options files

2023-11-14 00:37:53 +00:00

LICENSE

…

OWNERS

[infra] Add OWNERS to the Dart SDK

2022-02-14 14:06:34 +00:00

pubspec.yaml

Enable language 3.0 for analyzer_cli/.

2023-04-06 19:04:38 +00:00

README.md

Remove the legacy "_2" tests. \o/

2023-11-17 20:17:23 +00:00

README.md

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.