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

..

base

[analyzer] always show context messages for 'dart analyze'

2021-03-04 01:00:16 +00:00

flow_analysis

Replace CFE and analyzer legacy type promotion with a shared implementation.

2021-04-21 14:21:30 +00:00

messages

[vm/ffi] Array dimensions non-positive check in CFE

2021-04-27 06:56:28 +00:00

parser

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

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

scanner

Add TokenType.binaryOperatorOfCompoundAssignment, use instead of operatorFromCompoundAssignment().

2021-04-24 18:46:32 +00:00

sdk

Migrate _fe_analyzer_shared to null safety.

2020-12-12 03:22:29 +00:00

testing

Fix nullability issue in id_testing.

2021-03-18 11:00:58 +00:00

util

Fixes for review comments after _fe_analyzer_shared migration

2020-12-14 16:57:58 +00:00