Files

T

Johnni Winther 06bc0040cc [cfe] Migrate experimental flag libraries

Change-Id: I621925a41de02b09071e9c2fbbb608961e9879b3
Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/196496
Reviewed-by: Dmitry Stefantsov <dmitryas@google.com>
Commit-Queue: Johnni Winther <johnniwinther@google.com>

2021-04-23 09:55:41 +00:00

benchmarks/ikg

[kernel,front_end] Migrate first wave of pkg/kernel and pkg/front_end

2021-01-18 15:40:21 +00:00

lib

[cfe] Migrate experimental flag libraries

2021-04-23 09:55:41 +00:00

parser_testcases

[parser] More specific error messages when recovering new/const/Map/Set/List with said literals

2021-03-25 13:27:03 +00:00

test

[cfe] Add Extensions to the parser in the CFE type tests

2021-04-23 09:14:01 +00:00

testcases

[cfe] Instance field get for const functions.

2021-04-22 22:14:01 +00:00

tool

[cfe] Migrate experimental flag libraries

2021-04-23 09:55:41 +00:00

analysis_options_no_lints.yaml

[cfe] Refactor ClassHierarchyBuilder to use Tuple for computation

2021-01-19 19:52:13 +00:00

analysis_options.yaml

[CFE] Enable 'unrelated_type_equality_checks' lint

2020-10-02 11:22:27 +00:00

error_recovery.yaml

…

LICENSE

Update LICENSE

2021-04-07 10:28:38 +00:00

messages.status

[CFE] add 'Function' as type identifier check in CFE

2021-04-21 04:43:48 +00:00

messages.yaml

[CFE] add 'Function' as type identifier check in CFE

2021-04-21 04:43:48 +00:00

PRESUBMIT.py

…

pubspec.yaml

[kernel,front_end] Migrate first wave of pkg/kernel and pkg/front_end

2021-01-18 15:40:21 +00:00

README.md

Fix links in front_end readme

2020-12-07 15:02:57 +00:00

testing_with_lints.json

…

testing.json

[CFE] Include .crash_dart in weak tests; better handling of erroneous -D parameters and expectationFileMismatchSerialized on -DupdateExpectations=true

2021-03-19 13:34:17 +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 dart analyze command-line tool to analyze their Dart code.

Integrators that want to write tools that analyze Dart code should use the analyzer package.

Note: A previous version of this package was published on pub.dev. It has now been marked DISCONTINUED as it is not intended for direct consumption, as per the notes above.