Files

T

Jens Johansen 7ef0841386 [parser] Don't use potential type arguments if they came via recovery

A few places in the parser we call `computeTypeParamOrArg` and then
either use the result or not depending on whether there's a `(` after
it. That doesn't work well when `computeTypeParamOrArg` does recovery
by for instance inserting a > though.
This CL fixes that - at least in the places we know about.

Fixes #45848.

Change-Id: Id4b62b965131031f43c8ada0fe05045fc9834db3
Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/197360
Reviewed-by: Brian Wilkerson <brianwilkerson@google.com>
Reviewed-by: Johnni Winther <johnniwinther@google.com>
Commit-Queue: Jens Johansen <jensj@google.com>

2021-05-03 07:30:28 +00:00

lib/src

[parser] Don't use potential type arguments if they came via recovery

2021-05-03 07:30:28 +00:00

test

Flow analysis: implement "why not promoted" for binary/unary operator target.

2021-04-22 12:21:46 +00:00

tool

[CFE] Rename tests that require git; split unit_test_suites; filter tests better

2021-01-28 07:46:10 +00:00

analysis_options_no_lints.yaml

[cfe] Add id testing for inferred variable types

2021-04-15 05:06:56 +00:00

analysis_options.yaml

…

LICENSE

Update LICENSE

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

PRESUBMIT.py

[CFE] Spell check on kernel src; presubmit on kernel & _fe_analyzer_shared

2019-12-02 13:00:47 +00:00

pubspec.yaml

Prepare to publish analyzer 1.5.0 and _fe_analyzer_shared 21.0.0

2021-04-20 22:03:48 +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.