Jens Johansen
40777c001a
Currently, if a not-enabled-by-default experimental flag is on we allow formatting to fail. This means that when the flag is flipped there's a risk of failures as formatter crashes are now not allowed anymore. The failures for flipping the extension types / inline-class feature has caused crashes and was fixed before (twice!) in https://dart-review.googlesource.com/c/sdk/+/336001 https://dart-review.googlesource.com/c/sdk/+/335448 But naturally a new test was added after (https://dart-review.googlesource.com/c/sdk/+/336022) and we had a new failure on the flag-flip CL. This CL instead pretends like the inline-class flag is already flipped, in that the formatter is not allowed to crash because of it. That should make any new tests added before the flag is flipped that would otherwise cause a failure upon flag flip, fail, forcing the update of the status file. The status file is furtermore updated. Change-Id: Ifbc3d271a614e5dd747b35b252034087ad155a92 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/337321 Reviewed-by: Slava Egorov <vegorov@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.