| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
| |
Replace with LambdaType
|
|
|
|
| |
Replace with ParamRef
|
| |
|
|
|
|
|
| |
... to distinguish between HK(proxy) and *(ground) types.
Also, refactor some more methods to keep it DRY.
|
|
|
|
| |
Also, rename LambdaOver{Type,Term}s to {Type,Term}Lambda
|
| |
|
| |
|
| |
|
|
|
|
| |
Use an abstract type instead.
|
|
|
|
| |
Trying to bring PolyTypes closer to TypeLambdas
|
|
|
|
|
|
| |
MethodTypes have paramTypes whereas PolyTypes have paramBounds.
We now harmonize by alling both paramInfos, and parameterizing
types that will become common to both.
|
|
|
|
|
| |
and generalize MethodParam to ParamRef, and
TypeParamInfo to ParamInfo
|
|
|
|
|
| |
It was a red herring. Symbolic names are expanded anyway to $plus / $minus,
so they can't be confused with a variance prefix.
|
| |
|
|
|
|
| |
and fix typo
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|\
| |
| | |
Add "enum" construct
|
| | |
|
| |
| |
| |
| |
| | |
- rename utility methods
- generate utility methods also for object cases
|
| |
| |
| |
| |
| |
| | |
Infer type arguments for enum paraments from corresponding type
parameter bounds. This only works if the type parameter in question
is variant and its bound is ground.
|
| |
| |
| |
| | |
This commit can hopefully be reverted once #2121 is in.
|
| |
| |
| |
| |
| |
| |
| |
| | |
Support cases with type parameters that implicitly extend a non-parameterized base
without needing their own extends clause. The proposal has been updated to make clear
that this is supported.
Also address other reviewers comments.
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Based on the discussion in #1970, enumeration objects now
have three public members:
- valueOf: Map[Int, E]
- withName: Map[String, E]
- values: Iterable[E]
Also, the variance of case type parameters is now
the same as in the corresponding type parameter of
the enum class.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
In an enum case like
case C() extends P1 with ... with Pn ...
apply now returns `P1 & ... & Pn`, where before
it was just P1.
Also, add to Option test.
|
| |
| |
| |
| |
| | |
`copy` should always return the type of it's rhs. The discussion of
#1970 concluded that no special treatment for enums is needed.
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Flags like Trait are in fact not always defined when a symbol
is created. For symbols loaded from class files, this flag, and
some other is defined only once the classfile has been loaded.
But this happens in general before the symbol is completed.
We model this distinction by separating from the `FromStartFlags` set
a new set `AfterLoadFlags` and distinguishing between the two sets
in `SymDenotations#is`.
Test case is enum-Option.scala. This erroneously complained before
that `Enum` was not a trait.
|
| | |
|
| |
| |
| |
| |
| |
| | |
The same type needs to be used as a result type for
the copy method, and the function type implemented by
the companion module.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| | |
The previous scheme did not work because desugaring cannot deal with
repeated expansions. We now sidestep the issue by doing the expansion in the parser. Luckily,
positions work out perfectly, so that one can reconstruct the source precisely from the parsed untyped
trees.
|
| | |
|
| |
| |
| |
| | |
`enum' only allowed as a prefix of classes, dropped from traits and objects.
|
| |
| |
| |
| |
| | |
It's completely redundant, docstring is just the comment found
at the `start` offset, which is passed anyway.
|
| |
| |
| |
| | |
Modify syntax.md and Tokens/Parser/untpd to support enums.
|
| |
| |
| |
| | |
Insert an empty line before "where" in an explanation.
|
|\ \
| | |
| | | |
Fix #2024: TypeApply can be a final apply of a recursive method.
|
| | | |
|
| | |
| | |
| | |
| | |
| | | |
nullary methods with type parameters were handled wrongly,
which led to absence of type application and a cryptic error message.
|
| | |
| | |
| | |
| | | |
It saves tasty output near the class file output to a *.tasty-file.
|
|\ \ \
| | | |
| | | | |
Make leak avoidance more robust
|
| | |/
| |/|
| | |
| | |
| | |
| | | |
If class files are missing, finding an underlying class
reference might give a NoType. This caused an asInstanceOf
to fail. We now handle that case gracefully.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
`checkNoPrivateLeaks` can force a lot of things, this lead to
hard-to-reproduce issues in unpickling because we called
`checkNoPrivateLeaks` on the type parameters of a class before anything
in the class was indexed. We fix this by making sure that
`checkNoPrivateLeaks` never transforms type symbols, only term symbols,
therefore we can unpickle type parameters without forcing too many
things. tests/neg/leak-type.scala illustrates the new restriction that
this necessitates.
|
|\ \ \
| |/ /
|/| | |
Fixes `@unchecked` warnings
|