Adjusted generalized type alias feature spec to indicate ongoing discussion #88
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 feature specification for constructs like
typedef F<X> = List<X>;
was added a few days ago, but it turns out that we need to discuss one element of the design ("is it allowed to use a type alias as a class?, e.g.class C extends F<int> {}
,new F()
, whereF
denotes a type alias").This CL makes it explicit that that particular decision has not yet been made, and it indicates two likely outcomes of the discussion. This should be sufficient to put readers in a good position to understand what's going on.