Files

T

Dan Rubel ab229b30ef Improve fasta field recovery

In addition to improving field recovery, this CL
fixes class field recovery to include an endMember event event
and cleans up missing class body recovery.

Change-Id: I53afe5aef55452108803388de9245f7e14f97833
Reviewed-on: https://dart-review.googlesource.com/32820
Commit-Queue: Dan Rubel <danrubel@google.com>
Reviewed-by: Brian Wilkerson <brianwilkerson@google.com>

2018-01-06 21:51:50 +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

Improve fasta field recovery

2018-01-06 21:51:50 +00:00

test

Use --reify-generic-functions when running strong-mode tests with fasta

2018-01-05 16:15:48 +00:00

testcases

Don't add empty leading/trailing strings in multiline strings.

2018-01-05 17:01:49 +00:00

tool

Implement method type override checking rules in front_end.

2018-01-04 22:46: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

…

messages.yaml

Convert UNDEFINED_SUPER_METHOD errors.

2018-01-04 23:00:36 +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

…

testing.json

Start building incremental test suite

2017-12-01 13:03:16 +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.