| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| |
|
|
|
|
|
| |
Hacky but no-risk fix for #3189, which was caused by the ghost of
regular expression patterns rising from the grave to haunt the parser.
No review.
|
| | |
|
| | |
|
| |
|
|
|
|
| |
closes #3429
review by odersky
|
| |
|
|
|
|
| |
closes #3404
review by odersky
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
crashing-under-optimise test into pending since that looks like
a genuine bug - I'll open it a ticket. No review.
|
| |
|
|
|
|
| |
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.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
| |
Disabled scalacheck tests because they interfere with library
refactorings (refactorings break scalacheck).
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
| |
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.)
|
| | |
|
| |
|
|
|
|
|
|
| |
Tightened what gets specialized: only when the type parameter appears
at top level, or as a type argument to a Java array. For example T,
Array[T] cause specialization, but List[T] does not. Resurrected
spec-matrix, forgotten among the disabled tests. No review.
|
| |
|
|
|
|
| |
revert the revert of r21791 (fix constructor parameter annotations).
close #3390. together with a new starr it builds. no review.
|
| | |
|
| |
|
|
|
|
|
| |
revert commit that probably broke the build due to a bug in closure
elimination revert commit that reverted the commit that probably didn't
break the build
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Revert r21790: "closes #3373, #3177: validity check of an implicit "
value should consider the value as well as its accessor Revert r21792: "
"sorry, last-minute edit broke build: re-added parens "
will investigate how it broke and why my local pre-commit tests did not
catch the failure...
no review
|
| |
|
|
|
| |
fix and test where constructor parameter annotations end up. no review
|
| |
|
|
|
|
| |
closes #3373, #3177: validity check of an implicit value should consider
the value as well as its accessor review by odersky
|
| | |
|
| |
|
|
|
|
| |
Accumulate missing abstract member errors so they can all be printed
instead of only the first. Closes #2213, no review.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
Fixed bug in Iterator.iterate which would lead to a runtime exception
under some circumstances due to inadequate laziness in calculating the
next element. No review.
|
| | |
|
| |
|
|
|
| |
A small error message improvement suggested at #3092. No review.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
| |
Created TypeDiagnostics trait and have begun opportunistically moving
code into it. Along the way, some improvements to error messages.
The situation described in ticket #2206 has always had an applicable
error message, but it wasn't making it out to the user. More kinds of
ambiguity are disambiguated, see the test cases. And overload errors are
printed with some formatting so one has some hope of parsing. Review by
odersky.
|
| |
|
|
|
|
| |
Added test for several tickets that were fixed earlier this week. no
review.
|
| |
|
|
|
|
| |
Fixed construction of specialized classes in the presence of
side-effects and non-trivial initializers. Review by odersky.
|
| |
|
|
|
|
|
|
|
|
| |
fixed #3349 : method symbol cached too aggressively
cooking raw types changes a symbol's info, but the change was masked by
caching in MethodSymbol
review by odersky
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
StringBuilder no longer violates the Seq reverse contract: it returns
a new StringBuilder. The behavior formerly found in reverse (updates
in place) is now available in reverseContents. Migration warning on
reverse. Closes #3327.
Also did some StringBuilder rewriting as per discussion with odersky.
And took a cleaver to parts of the documentation to get to the good
parts a little faster. Review by community.
|
| |
|
|
|
|
| |
Took another of universal equality's victims to the hospital. Closes
#3348, no review.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Created Mutable and Immutable SetFactories to deal with the spectacular
performance regression which accompanies the use of AddingBuilder on
mutable Sets. Because '+' now creates a new collection even on mutable
sets, AddingBuilder on a 100K element collection will create garbage
sets of size 1,2,3...,99,999 before finishing. Thankfully there is
already GrowingBuilder.
See test/files/run/adding-growing-set.scala for a demonstration.
This patch is not complete: in particular, SortedSet and SetBuilder need
attention. Unfortunately there is a combinatorial jump in the number of
Addable/Growable divisions which arises once one tries to accomodate
both Sorted signatures (taking an Ordering) and unsorted signatures, so
will come back to it after receiving counsel.
Review by odersky.
|
