| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
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.
|
| |
|
| |
|
|
|
|
|
|
|
| |
Put dummy scalacheck dir in test/files since partest maddeningly
pre-fails the test suite if it's not present and git does not preserve
empty directories. No review.
|
|
|
|
|
|
| |
Misoptimization for list extractors caused non-sequences to incorrectly
match. Closes #3050, #2800. No review.
|
| |
|
| |
|
|
|
|
|
| |
Fixed a BigDecimal/Long comparison bug reported on the list. No review.
|
| |
|
| |
|
|
|
|
|
|
|
| |
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.
|