dart-sdk/pkg/front_end
Samir Jindel 28a0706e91 [kernel] Implement correct semantics of forwarding stubs in VM
This revision has been factored out of Revision 29300.

Change-Id: Idf579f0e5ffeea5764e2a9654c6812d69f6977c7
Reviewed-on: https://dart-review.googlesource.com/31921
Commit-Queue: Samir Jindel <sjindel@google.com>
Reviewed-by: Martin Kustermann <kustermann@google.com>
Reviewed-by: Paul Berry <paulberry@google.com>
2018-01-10 07:39:31 +00:00
..
benchmarks/ikg Smaller changes to incremental_perf.dart, this is preparation for the flutter IKG perf benchmark 2017-11-17 10:34:12 +00:00
example/incremental_reload [CFE] Move front-end API under src/ 2017-12-01 08:42:16 +00:00
lib/src [kernel] Implement correct semantics of forwarding stubs in VM 2018-01-10 07:39:31 +00:00
test Use --reify-generic-functions when running strong-mode tests with fasta 2018-01-05 16:15:48 +00:00
testcases Correct type arguments for NSM 2018-01-10 07:13:30 +00:00
tool Reland "Treat most warnings as errors in strong mode." 2018-01-08 09:20:02 +00:00
analysis_options.yaml Fix dynamic as bottom uses in front end and dart2js. 2017-10-30 19:54:26 +00:00
error_recovery.yaml Add error_recovery.yaml: a place to add scenarios we explicitly want to model in 2017-08-10 11:52:48 -07:00
LICENSE Create a README and pubspec for the front_end package. 2016-10-19 12:14:38 -07:00
messages.yaml Assign analyzer codes to several FrontEnd errors. 2018-01-09 21:25:48 +00:00
pubspec.yaml Add unstable API for bazel summary worker and move the actual worker out of package:front-end 2017-12-21 19:09:11 +00:00
README.md Prepare package:analyzer 0.30.0. 2017-05-03 14:34:55 -07:00
testing.json Add tests of instantiate to bound in fasta 2018-01-08 08:35:22 +00:00

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.