Files

T

Peter von der Ahé e1fe4d48a5 Remove type inferrer from generators

The type inferrer is no longer used (and wasn't necessary to begin
with, it should have been exposed via the helper object instead).

Also some other tweaks that should help me avoid merge conflicts.

Change-Id: I1f2aade93f9c836cc02dac6c002f48156caf2c76
Reviewed-on: https://dart-review.googlesource.com/74063
Reviewed-by: Jens Johansen <jensj@google.com>
Commit-Queue: Peter von der Ahé <ahe@google.com>

2018-09-10 09:05:59 +00:00

benchmarks/ikg

…

lib/src

Remove type inferrer from generators

2018-09-10 09:05:59 +00:00

test

Remove addCompileTimeError in favor of addProblem

2018-09-06 06:56:42 +00:00

testcases

Use LocatedMessage for invalid types

2018-09-06 10:25:15 +00:00

tool

Format constants and remove dart2jsCode

2018-08-30 08:05:31 +00:00

analysis_options.yaml

Update analysis options

2018-09-07 09:10:37 +00:00

error_recovery.yaml

…

LICENSE

…

messages.status

Revise with clause event handling

2018-09-07 19:33:51 +00:00

messages.yaml

[vm/kernel] Support CheckLibraryIsLoaded node in kernel constant evaluator

2018-09-07 19:32:11 +00:00

pubspec.yaml

[infra] Switch pkg bots to Dart 2

2018-08-13 07:04:06 +00:00

README.md

Prepare for analyzer 0.32.0.

2018-05-14 18:07:02 +00:00

testing.json

[VM] Turn dart2 on by default on the command line VM

2018-06-18 22:31:32 +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.