Closed
Description
Originally discussed in #38483.
We currently offer a quick fix to add an async
modifier if we parse await
in a non-async context when the await
is unambiguously an AwaitExpression:
However, we do not offer that quick fix if we parse await
in cases where it is ambiguous (such as in a call expression):
We should consider special-casing the error message for await
when it is ambiguous so that we can offer compatible quick fixes.