Files

T

Paul Berry 8f1ca007f2 Fix type inference for const expressions.

The inferred types for const expressions shouldn't refer to type
variables that are in scope, because at runtime those type variables
may take on different values at different times (meaning the const
expression isn't actually const after all).

Test cases are in inference_new, since analyzer implements incorrect
behavior.

Fixes #30677.

Change-Id: I27b9a95a92557ad1ce1c2c0f28d9a760c372d52a
Reviewed-on: https://dart-review.googlesource.com/5298
Reviewed-by: Konstantin Shcheglov <scheglov@google.com>

2017-09-12 21:43:49 +00:00

example/incremental_reload

Export ByteStore and its implementations from front_end.

2017-09-07 19:23:21 +00:00

lib

Fix type inference for const expressions.

2017-09-12 21:43:49 +00:00

test

Allow custom URI schemes in hot-reload unit test and internally in IKG and

2017-09-12 20:44:13 +00:00

testcases

Fix type inference for const expressions.

2017-09-12 21:43:49 +00:00

tool

don't use internal throwOnWarnings option

2017-09-01 13:52:48 -07:00

analysis_options.yaml

Disable supermixin support in front end and kernel.

2017-09-04 18:50:17 +00:00

BUILD.gn

Disable analysis on a few packages. (#29571 )

2017-05-05 22:06:00 -07: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

report abstract class member as separate error code

2017-09-07 20:58:44 +00:00

pubspec.yaml

More pre-publish changes

2017-08-25 14:22:57 -07:00

README.md

Prepare package:analyzer 0.30.0.

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

testing.json

Keep exported nodes during shaking.

2017-09-07 15:30:24 +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.