Files

T

Lasse Reichstein Holst Nielsen b3c12d4e3a Dart 2 Libraries Wave 3

Add `typeArguments` to Invocation.
Add constructors to Invocation, making it less necessary for users to create their own implementations.
Add tests.
Add Symbol.unaryMinus and Symbol.empty constants.

Change-Id: I70cb3265f9413617cf57fce1297e393a29eeb26a
Reviewed-on: https://dart-review.googlesource.com/40741
Commit-Queue: Lasse R.H. Nielsen <lrn@google.com>
Reviewed-by: Leaf Petersen <leafp@google.com>

2018-03-08 16:36:07 +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

Canonicalize representation of a message without location.

2018-03-08 12:58:17 +00:00

test

[fasta] Invalidate part file when init from dill

2018-03-06 10:19:01 +00:00

testcases

Dart 2 Libraries Wave 3

2018-03-08 16:36:07 +00:00

tool

Always create problems to ensure lines are removed from status files

2018-03-05 11:29:41 +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

Always create problems to ensure lines are removed from status files

2018-03-05 11:29:41 +00:00

messages.yaml

Report "missing statement" error on void

2018-03-01 21:04:48 +00:00

pubspec.yaml

Prepare for analyzer 0.31.2-alpha.0.

2018-02-14 21:22:54 +00:00

README.md

Prepare package:analyzer 0.30.0.

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

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.