Files

T

Konstantin Shcheglov 8a90e7a113 Explicitly disable colors in CompilerContext when run KernelDriver.

Running external processes while performing compiletion is crazily
expensive and surprising. This makes NonErrorResolverTest_Kernel about
2x faster (although still 2x slower than the current AnalysisDriver
implementation).

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

Bug:
Change-Id: I577fc15de50eeb7eba9454cb506bb2c30cd161ff
Reviewed-on: https://dart-review.googlesource.com/6660
Reviewed-by: Sigmund Cherem <sigmund@google.com>

2017-09-19 01:08:08 +00:00

example/incremental_reload

Export ByteStore and its implementations from front_end.

2017-09-07 19:23:21 +00:00

lib

Explicitly disable colors in CompilerContext when run KernelDriver.

2017-09-19 01:08:08 +00:00

test

Update front_end messages_test

2017-09-17 14:52:42 +00:00

testcases

Parse annotations for enums and named mixin applications.

2017-09-15 23:27:08 +00:00

tool

revise parser to use handleNativeClause

2017-09-14 13:25:48 +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

…

messages.yaml

Revert "Check whether type-arguments and type-parameters length match from the body builder."

2017-09-15 22:15:09 +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.