Paul Berry
8600df906e
This will allow diagnostic reporting code in the analyzer to be more easily converted to the new literate diagnostic reporting API, because it will make it possible to use `SourceRange` as the common denominator for situations where the location where a diagnostic needs to be reported might come from either a `SyntacticEntity` or a `SourceRange`. Change-Id: I6a6a6964f3ec2ea33e8900d93b5abe714c9e1dcc Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/467682 Reviewed-by: Brian Wilkerson <brianwilkerson@google.com> Reviewed-by: Johnni Winther <johnniwinther@google.com> Commit-Queue: Paul Berry <paulberry@google.com>
Front end for Dart
This package provides a low-level API for use by compiler back ends that wish to implement the Dart language. It is intended for eventual use by dev_compiler, dart2js, and the Dart VM. In addition, it will share implementation details with the analyzer package--this will be accomplished by having the analyzer package import (and re-export) parts of this package's private implementation.
End-users should use the dart analyze
command-line tool to analyze their Dart code.
Integrators that want to write tools that analyze Dart code should use the analyzer package.
Note: A previous version of this package was published on pub.dev. It has now been marked DISCONTINUED as it is not intended for direct consumption, as per the notes above.