Files

T

Johnni Winther 967673c005 [cfe] Introduce ClassMember

Use interface ClassMember instead of Builder in ClassHierarchyBuilder.
This avoids the coupling between DelayedMember and Builder and is a
precursor to removing Builder.target.

Change-Id: Ie2067512051618a60fcb94b5aae7e7f3d8c02b15
Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/119644
Commit-Queue: Johnni Winther <johnniwinther@google.com>
Reviewed-by: Aske Simon Christensen <askesc@google.com>

2019-10-03 09:49:01 +00:00

benchmarks/ikg

…

lib/src

[cfe] Introduce ClassMember

2019-10-03 09:49:01 +00:00

parser_testcases

[CFE] Update parser test framework to work with extensions

2019-10-03 08:29:51 +00:00

test

[cfe] Introduce ClassMember

2019-10-03 09:49:01 +00:00

testcases

[cfe] Use fileOffset in Forest instead of Token

2019-10-03 09:49:01 +00:00

tool

[vm/bytecode] Split AST and bytecode platform dill files

2019-09-23 23:08:41 +00:00

analysis_options_no_lints.yaml

[CFE] Parser test framework

2019-09-26 08:40:08 +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] Report error on extension members that conflict with Object members

2019-09-30 13:21:49 +00:00

messages.yaml

[cfe] Report error on extension members that conflict with Object members

2019-09-30 13:21:49 +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.38.4

2019-09-25 19:00:01 +00:00

README.md

…

testing_with_lints.json

[CFE] Add test that runs analyzer on CFE source with lints

2019-08-22 10:52:59 +00:00

testing.json

[CFE] Parser test framework

2019-09-26 08:40: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. In particular, there is no semver contract for release versions of this package. Please depend directly on individual versions.