Files

T

Johnni Winther 9c983d2ee3 [cfe] Support extensions via prefix

Change-Id: I6c1e69e5a5c83f5177754a350f5efbca9384972b
Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/124540
Auto-Submit: Johnni Winther <johnniwinther@google.com>
Commit-Queue: Sigmund Cherem <sigmund@google.com>
Reviewed-by: Sigmund Cherem <sigmund@google.com>

2019-11-08 19:53:00 +00:00

benchmarks/ikg

…

lib/src

[cfe] Support extensions via prefix

2019-11-08 19:53:00 +00:00

parser_testcases

[CFE] Parser: Don't report (recovered) operator as endClassConstructor

2019-11-06 09:42:37 +00:00

test

[cfe] Support extensions via prefix

2019-11-08 19:53:00 +00:00

testcases

[cfe] Support extensions via prefix

2019-11-08 19:53:00 +00:00

tool

[kernel] Deprecate Library.isExternal

2019-11-04 09:24:02 +00:00

analysis_options_no_lints.yaml

Exclude shared integration test suites from analysis.

2019-10-31 17:13:53 +00:00

analysis_options.yaml

[CFE] First batch of fixes for requiring explicit types

2019-08-15 13:13:20 +00:00

error_recovery.yaml

…

LICENSE

…

messages.status

[cfe] Support extensions via prefix

2019-11-08 19:53:00 +00:00

messages.yaml

[cfe] Support extensions via prefix

2019-11-08 19:53:00 +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.39.1.

2019-10-31 15:44:23 +00:00

README.md

…

testing_with_lints.json

Flow analysis: introduce ID tests for AssignedVariables.

2019-10-25 13:44:05 +00:00

testing.json

[cfe+analyzer] Move messages, scanner and parser to package:_fe_analyzer_shared

2019-11-01 09:37:57 +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.