Files

T

Paul Berry cded10154c Fix type inference of compound assignments when getter/setter have different types.

For compound assignments, we need to look up the "combiner" operation
in the type of the getter (not the setter), since the receiver of the
combiner operation is the value that was read.  This is necessary for
soundness.

Change-Id: I02e0e93310b6b6b94d4a6253d4cf2fc1d3c69cd5
Reviewed-on: https://dart-review.googlesource.com/16607
Reviewed-by: Konstantin Shcheglov <scheglov@google.com>
Commit-Queue: Paul Berry <paulberry@google.com>

2017-10-25 18:54:17 +00:00

benchmarks/ikg

Update incremental_perf.dart to use named changesets, add IKG benchmarks

2017-10-12 11:17:48 +00:00

example/incremental_reload

Remove compiling platform.dill from patch_sdk.dart

2017-10-06 15:34:37 +00:00

lib

Fix type inference of compound assignments when getter/setter have different types.

2017-10-25 18:54:17 +00:00

test

Implement FlutterByteStore with temporary protected keys.

2017-10-24 20:07:00 +00:00

testcases

Fix type inference of compound assignments when getter/setter have different types.

2017-10-25 18:54:17 +00:00

tool

[kernel] Don't serialize external libraries for vmservice_io.dill

2017-10-25 11:51:41 +00:00

analysis_options.yaml

Disable supermixin support in front end and kernel.

2017-09-04 18:50:17 +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.yaml

Check if target of redirecting factory is constructor of abstract class

2017-10-25 12:23:39 +00:00

pubspec.yaml

Fix SDK constraints on analyzer, front_end, kernel, meta

2017-09-28 19:33:27 +00:00

README.md

…

testing.json

Skip DDC when running front end analyzer checks.

2017-10-18 21:36:08 +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.