languages/dart-sdk
languages/dart-sdk
1
0
Fork 0
mirror of https://github.com/dart-lang/sdk synced 2024-07-20 18:05:01 +00:00
Code Issues Actions 1 Packages Projects Releases Wiki Activity
dart-sdk/pkg/front_end
History
Kallen Tu 134839098b Serialization/Deserialization for Variance in Type Parameters. 
Change-Id: I9bce86293c23c4b9d2b8011e866f04bcab80e74a
Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/118881
Reviewed-by: Jens Johansen <jensj@google.com>
Reviewed-by: Dmitry Stefantsov <dmitryas@google.com>
Commit-Queue: Kallen Tu <kallentu@google.com>
2019-09-27 16:57:00 +00:00
..
benchmarks/ikg
lib/src [CFE] Avoid talking about const context in error messages. 2019-09-27 14:49:57 +00:00
parser_testcases [parser] Fix bug wrt when the handleNonNullAssertExpression is added 2019-09-27 11:53:15 +00:00
test Added variance support in listeners to ast. 2019-09-26 18:11:10 +00:00
testcases Serialization/Deserialization for Variance in Type Parameters. 2019-09-27 16:57:00 +00:00
tool [vm/bytecode] Split AST and bytecode platform dill files 2019-09-23 23:08:41 +00:00
analysis_options.yaml [CFE] First batch of fixes for requiring explicit types 2019-08-15 13:13:20 +00:00
analysis_options_no_lints.yaml [CFE] Parser test framework 2019-09-26 08:40:08 +00:00
error_recovery.yaml
LICENSE
messages.status [CFE] Avoid talking about const context in error messages. 2019-09-27 14:49:57 +00:00
messages.yaml [CFE] Avoid talking about const context in error messages. 2019-09-27 14:49:57 +00:00
PRESUBMIT.py [CFE] Add PRESUBMIT.py that runs a little smoke testing 2019-08-16 12:28:07 +00:00
pubspec.yaml Prepare to publish analyzer 0.38.4 2019-09-25 19:00:01 +00:00
README.md
testing.json [CFE] Parser test framework 2019-09-26 08:40:08 +00:00
testing_with_lints.json [CFE] Add test that runs analyzer on CFE source with lints 2019-08-22 10:52:59 +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. In particular, there is no semver contract for release versions of this package. Please depend directly on individual versions.