dart-sdk/pkg/front_end
Paul Berry 41170b0a15 When reordering constructor initializers, use correct types for temp vars.
In strong mode, when a call to a super-initializer is reordered, we
can use the static type of the super-initializer arguments to set the
types of the temporary variables that we use to do the reordering.
This is desirable because it might help avoid unnecessary casts.

In non-strong mode, we use `dynamic` for the temporary variables, to
replicate Dart 1.0 behavior.

R=scheglov@google.com

Review-Url: https://codereview.chromium.org/2993193002 .
2017-08-07 13:55:40 -07:00
..
example/incremental_reload Move byte_store.dart and file_byte_store.dart to their own subdirectory. 2017-08-07 11:04:48 -07:00
lib When reordering constructor initializers, use correct types for temp vars. 2017-08-07 13:55:40 -07:00
test Replace fake directories with actual createDirectory(). 2017-08-07 13:25:16 -07:00
testcases When reordering constructor initializers, use correct types for temp vars. 2017-08-07 13:55:40 -07:00
tool Switch FE to use the libraries.json format. 2017-08-07 08:41:28 -07:00
analysis_options.yaml
BUILD.gn
LICENSE
messages.yaml Switch FE to use the libraries.json format. 2017-08-07 08:41:28 -07:00
pubspec.yaml
README.md
testing.json

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.