Lasse R.H. Nielsen
ff5f391c0a
Make API more consistent for a few methods. Reduce the number of language features used in tests: * Never iterating an iterable, always converting it using `.toList()` first and iterating using indices (fx `setEquals`). Also require a `List` in places where an `Iterable` wasn't necessary. * Avoid doing complicated computations that are also used for the error message. Do simple check first, then recompute to get better error messages (fx `allDistinct`). Renamed some rarely used members for consistency (`stringContainsInOrder`->`containsInOrder`, where other string-contains functions just start with `contains`, and `containsOneOf` -> `containsAny` to match `Iterable.any` phrasing, and also it accepts if containing at least one, not precisely one.) Removed a function that wasn't used anywhere. Moved `assertStatementsEnabled` to `variations.dart` as `asserts`. Removed `typeAssertionsEnabled` and `checkedModeEnabled`. The former used in one place, where it was replaced with `checkedImplicitDowncasts` from `variations.dart`, the latter wasn't used anywhere. Deprecates `package:expect/minitest.dart`. It was never intended to be used for new tests, only as a help to convert existing tests written against `package:unit_test`. All existing imports marked as `// ignore: deprecated_member_use`. Change-Id: I07e21d4c0f3ccf11b82ee34af2668fdbb22264d2 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/352360 Reviewed-by: Slava Egorov <vegorov@google.com> Reviewed-by: Ömer Ağacan <omersa@google.com> Reviewed-by: Nate Bosch <nbosch@google.com> Reviewed-by: Stephen Adams <sra@google.com> Commit-Queue: Lasse Nielsen <lrn@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.