Jens Johansen
29782f8750
These ease my life slightly. Examples: Compile to executable to get faster runs: ``` out/ReleaseX64/dart-sdk/bin/dart compile exe pkg/front_end/tool/gitformat_cl.dart -o ~/bin/format_cl out/ReleaseX64/dart-sdk/bin/dart compile exe pkg/front_end/tool/git_branch_helper.dart -o ~/bin/gitbranch ``` Now I can format my entire CL with ``` $ format_cl Using file:///path/to/dart-sdk/sdk/out/ReleaseX64/dart stdout> Formatted 3 files (0 changed) in 0.35 seconds. ``` and get info about my branching with ``` $ gitbranch ├── origin/main │ ├── add_a_few_cfe_util_tools [ahead 2] ``` Change-Id: I2e89196ab702660a1486894d22678e3cd0c07994 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/352641 Reviewed-by: Chloe Stefantsova <cstefantsova@google.com> Commit-Queue: Jens Johansen <jensj@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.