dart-sdk/pkg/front_end
danrubel 6f6689889c Update fasta parser to report ParserErrorCode.FUNCTION_TYPED_PARAMETER_VAR
In addition to adding missing errors, this CL inlines modifier parsing
as part of a multi step effort to parse modifiers once and provide
better error recovery for class member and top level declarations.

Change-Id: Ibea91a4a3e2073ed6079f0f44ff4bbbb4a98a614
Reviewed-on: https://dart-review.googlesource.com/35300
Reviewed-by: Brian Wilkerson <brianwilkerson@google.com>
Commit-Queue: Dan Rubel <danrubel@google.com>
2018-01-17 18:28:48 +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 Update fasta parser to report ParserErrorCode.FUNCTION_TYPED_PARAMETER_VAR 2018-01-17 18:28:48 +00:00
test Deprecate IncrementalClassHierarchy 2018-01-17 13:30:17 +00:00
testcases Fix handling of forwarding semi-stubs in the front end. 2018-01-17 17:47:58 +00:00
tool Handle file names correctly on Windows 2018-01-17 14:11:30 +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 Create a README and pubspec for the front_end package. 2016-10-19 12:14:38 -07:00
messages.yaml Update fasta parser to report ParserErrorCode.FUNCTION_TYPED_PARAMETER_VAR 2018-01-17 18:28:48 +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 Prepare package:analyzer 0.30.0. 2017-05-03 14:34:55 -07:00
testing.json Deprecate IncrementalClassHierarchy 2018-01-17 13:30:17 +00:00

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.