Correct grammar rule for <typeNotVoidNotFunction>
to allow prefix
#3492
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Thanks to @modulovalue for reporting this grammar fault!
It is possible to import 'dart:core' with a prefix
p
. This causes the built-in classFunction
to be denoted by the termp.Function
(whereas the plain identifierFunction
is a lookup failure, or it denotes something else, or it actually works because we're also explicitly importing 'dart:core' without a prefix).In any case, we should allow
p.Function
in the grammar. This PR changes said grammar rule such that this is achieved.