Files

T

Konstantin Shcheglov 7f33f78026 Issue 30875. Don't damage _redirecting# when adding kernels to DillLoader.

R=ahe@google.com, paulberry@google.com, sigmund@google.com

Bug: https://github.com/dart-lang/sdk/issues/30875
Change-Id: Iede037673458131a357050ab61eb9930b70d372b
Reviewed-on: https://dart-review.googlesource.com/8381
Reviewed-by: Peter von der Ahé <ahe@google.com>
Commit-Queue: Konstantin Shcheglov <scheglov@google.com>

2017-09-26 20:41:14 +00:00

example/incremental_reload

Move reload.dart to test directory.

2017-09-21 13:43:02 +00:00

lib

Issue 30875. Don't damage _redirecting# when adding kernels to DillLoader.

2017-09-26 20:41:14 +00:00

test

Issue 30875. Don't damage _redirecting# when adding kernels to DillLoader.

2017-09-26 20:41:14 +00:00

testcases

Catch URI parse failure and report error

2017-09-26 11:26:20 +00:00

tool

Move command_line.dart and most of compile_platform.dart into lib/

2017-09-26 17:34:01 +00:00

analysis_options.yaml

Disable supermixin support in front end and kernel.

2017-09-04 18:50:17 +00:00

BUILD.gn

Disable analysis on a few packages. (#29571 )

2017-05-05 22:06:00 -07: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

Catch URI parse failure and report error

2017-09-26 11:26:20 +00:00

pubspec.yaml

More pre-publish changes

2017-08-25 14:22:57 -07:00

README.md

Prepare package:analyzer 0.30.0.

2017-05-03 14:34:55 -07:00

testing.json

Keep exported nodes during shaking.

2017-09-07 15:30:24 +00:00

README.md

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.