Konstantin Shcheglov
921ec7f507
Replace the positional Scanner constructors with a single constructor that takes the input text and error reporting callback as named required arguments. Remove the unused fasta forwarding constructor, reader offset handling, and stored first token. The scanner now keeps only the input text and returns the token stream directly from tokenize. Update analyzer, analysis server, plugin, CLI, scrape, and scanner test call sites to use the named constructor arguments. Change-Id: Ieabb7b28570d4a963563fb2d1c5ef5ac0c89032a Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/500340 Reviewed-by: Johnni Winther <johnniwinther@google.com> Reviewed-by: Bob Nystrom <rnystrom@google.com> Reviewed-by: Brian Wilkerson <brianwilkerson@google.com> Reviewed-by: 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.