a539d2ef5f
The CL is reverted because it didn't account for the case when a check of a user-specified type argument against the bound depends on another type that is only known after type inference is done. Change-Id: I1fd140af95ed37b9191a5b161a281d4639e3453f Reviewed-on: https://dart-review.googlesource.com/c/79048 Commit-Queue: Dmitry Stefantsov <dmitryas@google.com> Reviewed-by: Aske Simon Christensen <askesc@google.com> |
||
|---|---|---|
| .. | ||
| benchmarks/ikg | ||
| lib/src | ||
| test | ||
| testcases | ||
| tool | ||
| analysis_options.yaml | ||
| error_recovery.yaml | ||
| LICENSE | ||
| messages.status | ||
| messages.yaml | ||
| pubspec.yaml | ||
| README.md | ||
| testing.json | ||
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 [dartanalyzer][analyzercli] command-line tool to analyze their Dart code.
Integrators that want to write tools that analyze Dart code should use the [analyzer] package.
Note: The APIs in this package are in an early state; developers should be careful about depending on this package. In particular, there is no semver contract for release versions of this package. Please depend directly on individual versions.