021b4a0bc8
We don't support invalidating `dart:` libraries, so there's no reason to include such libraries in the computeReusedLibraries calculations: They should aways be reused. This CL does exactly that. On 430 flutter tests, it changes the time it takes to execute `computeReusedLibraries` by -15.7188% +/- 8.83679% (-193.125 ms +/- 108.571 ms for all 430 tests) (at 95% confidence). Said another way it reduces the average runtime for computeReusedLibraries from ~2.8 ms to ~2.4 ms. Change-Id: I23a68d4910c81be94b8d9d29495e63546bdad23f Reviewed-on: https://dart-review.googlesource.com/52441 Commit-Queue: Jens Johansen <jensj@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.