dart-sdk/pkg/front_end
Kevin Millikin e1bf9c3e88 Remove void as an exported name from dart:core
`void` will be a reserved word in Dart 2.0 (it always was in Dart 1.x).
Remove it as an exported name from dart:core because it could be
accidentally hidden.

Bug: https://github.com/dart-lang/sdk/issues/31480
Change-Id: Id804cccbc144f3c8ba2fc9898a3b5c79e238ab36
Reviewed-on: https://dart-review.googlesource.com/24940
Reviewed-by: Peter von der Ahé <ahe@google.com>
Commit-Queue: Kevin Millikin <kmillikin@google.com>
2017-12-01 16:28:16 +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 Remove void as an exported name from dart:core 2017-12-01 16:28:16 +00:00
test Start building incremental test suite 2017-12-01 13:03:16 +00:00
testcases Remove void as an exported name from dart:core 2017-12-01 16:28:16 +00:00
tool Route all messages through Loader. 2017-12-01 11:38:26 +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 Route all messages through Loader. 2017-12-01 11:38:26 +00:00
pubspec.yaml Update front_end and kernel before publishing 2017-11-28 19:28:24 +00:00
README.md Prepare package:analyzer 0.30.0. 2017-05-03 14:34:55 -07:00
testing.json Start building incremental test suite 2017-12-01 13:03:16 +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.