Encode variances in parameter names #2103
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This leads to a slight overall simplification, harmonizes pickle format with internal representation, and makes MethodTypes and PolyTypes more similar to each other. I believe the change is useful as it is, but in particular it is a useful step for an eventual unification of MethodTypes and PolyTypes.
|
That's a very nice simplification! |
smarter
reviewed
Mar 14, 2017
| @@ -241,6 +241,12 @@ object desugar { | |||
| * class C { type v C$T; type v T = C$T } | |||
| */ | |||
| def typeDef(tdef: TypeDef)(implicit ctx: Context): Tree = { | |||
| val name = | |||
| if (tdef.name.hasVariance && tdef.mods.is(Param)) { | |||
| ctx.error(em"type parameter name may not start with `+' or `-'", tdef.pos) | |||
There was a problem hiding this comment.
Is this even allowed by the parser?
There was a problem hiding this comment.
Yes, ++, -- are legal parameter names.
smarter
reviewed
Mar 14, 2017
| class PolyType(val paramNames: List[TypeName], val variances: List[Int])( | ||
| /** A type lambda of the form `[X_0 B_0, ..., X_n B_n] => T` | ||
| * This is used both as a type of a polymorphic method and as a type of | ||
| * a higher-kidned type parameter. Variances are encoded in parameter |
and fix typo
It was a red herring. Symbolic names are expanded anyway to $plus / $minus, so they can't be confused with a variance prefix.
Merged
|
Superseded by #2121 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This leads to a slight overall simplification, harmonizes pickle
format with internal representation, and makes MethodTypes and
PolyTypes more similar to each other.
I believe the change is useful as it is, but in particular it is
a useful step for an eventual unification of MethodTypes and
PolyTypes.