Files

T

Dan Rubel d26c310a27 Rework parsing of local const declarations

Similar to earlier work that reworked parsing of variable declarations,
this CL reworks parsing of local constant declarations to use
TypeInfo rather than parseType. This simplifies and improves recovery,
and reduces the number of error messages in some recovery situations.

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

2018-03-20 22:50:20 +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

lib/src

Rework parsing of local const declarations

2018-03-20 22:50:20 +00:00

test

Update names derived from Program

2018-03-16 09:33:07 +00:00

testcases

Add expectation.

2018-03-15 13:50:57 +00:00

tool

Update names derived from Program

2018-03-16 09:33:07 +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.status

Report a compile-time error on magic const

2018-03-13 19:07:12 +00:00

messages.yaml

Report a compile-time error on magic const

2018-03-13 19:07:12 +00:00

pubspec.yaml

Do the rounds for new analyzer publish + fix analyzer_plugin.

2018-03-12 23:02:29 +00:00

README.md

…

testing.json

Add testing chain to validate messages.yaml

2018-02-28 11:02:23 +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.