| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
| |
Parse ordering issue prevented passing properties containing a :. There
is a test case included, but note that partest passes it with or without
the patch: see ticket #3712. Closes #3495, no review.
|
| | |
|
| |
|
|
|
|
| |
closes #3622: refchecks erased types without uncurrying them first
review by odersky
|
| |
|
|
|
| |
review by prokopec
|
| |
|
|
|
|
|
|
|
| |
fixed by having mixin do the cloning at the beginning of erasure and
then updating the symbol's info to transform it to be valid in current
phase
review by odersky
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
note that all type parameters must be reported in error messages about
failing type inference, but only type parameters that were inferred
successfully should be substituted
the idea of mapping type parameter symbols to the corresponding type
ref in order to make substitution the identity does not seem to work,
leading to errors like:
src/library/scala/collection/immutable/SortedMap.scala:38:
error: type mismatch; found :
scala.collection.immutable.SortedMap[A,B(in method empty)]
required: scala.collection.immutable.SortedMap[A,B(in trait
SortedMap)]
override def empty: SortedMap[A, B] = SortedMap.empty
^
(I guess that's why they were retracted before, but that wasn't done consistently, leading to #3152 -- my first attempt at fixing the latter lead to this bug... I've assigned #3152 to you Martin, as I can't decide how to fix it.)
review by odersky
|
| |
|
|
|
| |
review by odersky
|
| |
|
|
|
| |
review by dragos
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
closes #2331: the pre-transform in Erasure did not correctly recurse in
the case of a TypeApply.
It simply returned the function, which might very well have been, say,
a Select node, which had to be erased in case the qualifier's type is a
refinement.
(sorry about the whitespace changes)
review by odersky
|
| | |
|
| |
|
|
|
| |
(That's right, multiple two digit tickets.)
|
| |
|
|
|
|
| |
A crasher in the pattern matcher revealed a flaw in how equality
comparisons were constructed. Closes #3570, no review.
|
| |
|
|
|
|
|
|
| |
Test case for #1974, which was fixed at some point even though martin
says in the comments it wouldn't be fixed for 2.8. Take that, things
which think they won't be fixed which really will be. Closes #1974, no
review.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
| |
The inliner now looks harder for method implementations. In addition
to the receiver, it will find those in directly mixed in traits and
in superclasses. It still won't find those in traits mixed only into
superclasses, as that didn't come quite so easily. Closes #3234 but I'll
be opening up another ticket. Review by dragos.
|
| |
|
|
|
|
|
|
| |
A wholesale reversion of the pattern matcher to r21939, motivated by
the appearance of #3578. Closes #3578, reopens #2800, #3050. Review by
moors. (I can't keep saying "no review" when every move I make in here
seems to break something.)
|
| |
|
|
|
|
| |
Disables NotNull checking unless -Ynotnull is given. Closes #3568,
review by odersky.
|
| | |
|
| |
|
|
|
|
| |
Made getters treated more like private members when debating whether to
inline. Closes #3420, review by dragos.
|
| |
|
|
|
|
| |
compile because the specialized variants of apply were not implemented
as well. Fixed by extending runtime.AbstractFunction0 instead.
|
| |
|
|
|
|
|
|
| |
Taking another shot at negative constants as annotation arguments since
r22175 didn't quite get there. I call into the constant folder with the
unfolded tree at the last point before it's going to fail the compile
anyway. Closes #3521, review by odersky.
|
| |
|
|
|
|
|
| |
Patch from Jason Zaugg so singleton types aren't accidentally deprived
of a fourth try at satisfaction. Already reviewed by odersky, so no
review.
|
| |
|
|
|
|
|
| |
Reverts r21973, the patch I characterized as "hacky but no-risk" in my
commit message, for causing #3480. Closes #3480. I'd say no review but
who can trust a guy who throws around "no risk" with such abandon.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
according to my tests, they all currently work.
|
| | |
|
| |
|
|
|
| |
attention in case the ticket was being left open intentionally.)
|
| | |
|
| |
|
|
|
|
| |
Added tests for bugs which have been fixed since beta1. Closes #2691,
#3020. No review.
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
Moved the test for #3420 to pending and reopened the ticket. The bug
only materializes if scalac was itself built with -optimise. (We may
need a richer language for describing optimise bugs.) No review.
|
| |
|
|
|
|
| |
Make the inliner be more careful about where it pokes around. Closes
#3252, #3430. Review by dragos.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
| |
closes #3429
review by odersky
|
| |
|
|
|
|
| |
closes #3404
review by odersky
|
| | |
|
| | |
|
| |
|
|
|
|
| |
Removed an assertion which was asserting an untrue statement thus
causing chaos and strife. Closes #3411, no review.
|
| |
|
|
|
|
|
|
| |
Overhauled sequence length logic in the pattern matcher. Removes
unnecessary boxing and a few varieties of wrongness.
Closes #3395, #3150, #2958, #2945, #2187. No review.
|
| |
|
|
|
|
| |
Closes #3424, double definition when overriding a generic method with
specialized types, inherited from a specialized class. no review.
|
| | |
|
| |
|
|
|
|
|
|
| |
changes necessary to plug it back in while preserving everything which
has happened since then in tests and such, but we should be the lookout
for overreversion. Review by phaller (but as a formality, I don't think
it requires direct review.)
|
| | |
|
