Files

T

Konstantin Shcheglov ada4db3fb6 When using SDK outline, transplant its names into the name root.

It's a bit messy that we have to break immutability of CanonicalName(s)
here. The alternative is not re-load SDK outline from bytes every time.
It is relatively expensive for small tests, although probably relatively
less expensive for large apps when we load hundreds of other libraries.

Thoughts?

R=ahe@google.com, paulberry@google.com, sigmund@google.com
BUG= https://github.com/dart-lang/sdk/issues/30409

Review-Url: https://codereview.chromium.org/2995773002 .

2017-08-11 12:00:37 -07:00

example/incremental_reload

Add IncrementalKernelGenerator.acceptLastDelta()/rejectLastDelta().

2017-08-10 12:28:14 -07:00

lib

When using SDK outline, transplant its names into the name root.

2017-08-11 12:00:37 -07:00

test

When using SDK outline, transplant its names into the name root.

2017-08-11 12:00:37 -07:00

testcases

Implement type inference for named function expressions.

2017-08-08 10:02:19 -07:00

tool

Switch FE to use the libraries.json format.

2017-08-07 08:41:28 -07:00

analysis_options.yaml

Move kernel baseline tests to front_end.

2017-04-19 10:57:58 +02: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

Switch FE to use the libraries.json format.

2017-08-07 08:41:28 -07:00

pubspec.yaml

front_end analyzer dev dependency.

2017-07-28 06:38:10 -07:00

README.md

Prepare package:analyzer 0.30.0.

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

testing.json

Remove the "kompile" mode of running the front end.

2017-07-13 10:52:55 -07: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.