Paul Berry
d8fc3630cf
Note: I removed the exception wrapping code as part of the migration. Rationale: this function performs a small task and has been operating successfully for a long time; removing the exception wrapping code avoids making front_end dependent upon AnalysisException and CaughtException at this time. In the unlikely event that an exception occurs in this function, we still have many avenues available for tracking down the problem: examine the stack trace of the exception, isolate a repeatable test case (if the exception happened in e.g. command-line analyzer), or reproduce the exception from file state information recorded by the AnalysisDriver (if the exception happened in analysis server). R=scheglov@google.com Review-Url: https://codereview.chromium.org/2668553002 .
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.