Files

T

Paul Berry 043f18f843 Flow analysis: use a callback to check if a property is promotable.

Previously we expected the client to provide a set of promotable
fields, which worked well for testing.  But using a callback gives the
client more flexibility (e.g. it would allow field promotability to be
computed on demand based on other data).

Bug: https://github.com/dart-lang/language/issues/2020
Change-Id: I40683a4c19a17147e86f0faa1339aa025da35229
Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/256962
Reviewed-by: Konstantin Shcheglov <scheglov@google.com>
Commit-Queue: Paul Berry <paulberry@google.com>

2022-09-22 13:09:07 +00:00

benchmark

Import exhaustiveness checker prototype into _fe_analyzer_shared.

2022-05-17 17:46:39 +00:00

lib/src

Flow analysis: use a callback to check if a property is promotable.

2022-09-22 13:09:07 +00:00

test

Flow analysis: use a callback to check if a property is promotable.

2022-09-22 13:09:07 +00:00

tool

Change : to = for default values in pkg.

2022-08-24 15:57:16 +00:00

analysis_options_no_lints.yaml

[cfe] Add macro api test

2022-02-10 16:08:00 +00:00

analysis_options.yaml

Change SDK constraint for _fe_analyzer_shared to 2.17.0.

2022-06-29 19:31:55 +00:00

LICENSE

Update LICENSE

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

OWNERS

[infra] Add OWNERS to the Dart SDK

2022-02-14 14:06:34 +00:00

PRESUBMIT.py

[python3] Migrate PRESUBMIT.py files

2021-08-16 08:29:54 +00:00

pubspec.yaml

Prepare to publish analyzer 5.0.0 and _fe_analyzer_shared 48.0.0

2022-09-12 19:37:09 +00:00

README.md

…

README.md

FE/analyzer shared code

This package contains logic that is shared between the front_end and analyzer packages. It is intended solely to facilitate development of the Dart SDK, and is not intended for use by end users. In particular, this package has no public API, so no guarantee is made of compatibility between one version of the package and the next.

End users should consider using the analyzer package to analyze Dart source code.