Files

T

Paul Berry 38cab10852 Patterns parsing: track when variable patterns are in an assignment context.

Variable patterns behave so differently inside a patternAssignment
that we may want to represent them using different AST nodes inside
the analyzer/CFE.  This change adds a boolean flag allowing the
implementation to know what kind of variable pattern it's looking at
when parsing occurs.

Bug: https://github.com/dart-lang/sdk/issues/50035
Change-Id: I60adf2865bbe24f85b72a79b1360833bf823bd67
Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/273829
Reviewed-by: Konstantin Shcheglov <scheglov@google.com>
Commit-Queue: Paul Berry <paulberry@google.com>
Reviewed-by: Jens Johansen <jensj@google.com>

2022-12-07 22:45:40 +00:00

benchmark

Import exhaustiveness checker prototype into _fe_analyzer_shared.

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

lib/src

Patterns parsing: track when variable patterns are in an assignment context.

2022-12-07 22:45:40 +00:00

test

Shared analysis testing: Distinguish Var.errorId from variable identity.

2022-12-07 22:10:35 +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

Enable annotate_overrides lint in _fe_analyzer_shared/

2022-11-17 15:13:39 +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.3.0 and _fe_analyzer_shared 51.0.0

2022-12-07 22:18:37 +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.