43c8d637bd
Unclear, if this was intentionally written as classes. It just seemed confusing to me. Since the classes were essentially functions that had some of their arguments passed in the constructor and some of their arguments passed in a method call. It also seemed impossible to reuse the actual objects. Change-Id: I56b341ee4851d24b9d176857a53b96f7eb941335 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/317883 Commit-Queue: Jonas Jensen <jonasfj@google.com> Reviewed-by: Phil Quitslund <pquitslund@google.com> |
||
|---|---|---|
| .. | ||
| bin | ||
| lib | ||
| test | ||
| tool | ||
| .gitignore | ||
| analysis_options.yaml | ||
| LICENSE | ||
| OWNERS | ||
| pubspec.yaml | ||
| 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_2 language_2
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.