Adjust 'Type Aliases' to outlaw explicit type arguments in static method call #1672
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.
The current text in the section 'Type Aliases' in the language specification implies that it is possible to invoke a static method
staticMethod
of a classC
via a type aliasF
with type arguments:This should be an error, and the tests expect that it is an error, but the spec language said otherwise. This PR changes the spec text to follow the intention and tests, and makes it an error to include type arguments in this kind of static method invocation.
It also changes the grammar such that a type alias can denote a
<type>
rather than just a<functionType>
, hence "enabling" non-function type aliases in general.