| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
| |
different from the other errors, so no second try was done for them.)
|
| |
|
| |
|
|
|
|
|
|
| |
added support for continuations in try/catch blocks. review by
community.
|
|
|
|
|
|
| |
fixed treatment of annotated types in isNumericSubType. re-enabled test
case. review by odersky
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Leveraged -Xmigration to burn off some warts which arose in the new
collections. Warnings put in place for behavioral changes, allowing the
following. 1) Buffers: create new collections on
++ and -- like all the other collections. 2) Maps: eliminated
never-shipped redundant method valuesIterable and supplied these
return types:
def keys: Iterable[A]
def keysIterator: Iterator[A]
def values: Iterable[B]
def valuesIterator: Iterator[B]
def keySet: Set[A]
I concluded that keys should return Iterable because keySet also exists
on Map, and is not solely in the province of Maps even if we wanted to
change it: it's defined on Sorted and also appears in some Sets. So it
seems sensible to have keySet return a Set and keys return the more
general type.
Closes #3089, #3145. Review by odersky.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
closes #3152: refactored adjustTypeArgs and methTypeArgs so that tparams
are correctly split into ones that were inferred successfully, and
that thus have a corresponding type argument, and those that weren't
determined
I didn't investigate the exact cause of the final error message in the
bug report, but Jason Zaugg's observations seems correct and I never
liked that uninstantiated buffer in the first place.
review by odersky
|
| |
|
| |
|
|
|
|
|
|
| |
Temporarily disabling failing test until I can finish my partest work.
No review.
|
|
|
|
|
|
|
|
|
|
| |
tests you have placed in the test/debug directories - critically
for those of us stuck debugging ant, this lets one run a small
selection of tests by way of ant instead of the console runner.
(Sorry about the empty .gitignore files, but one of git's quirks is that
it won't acknowledge the existence of an empty directory.) No review.
|
|
|
|
|
|
| |
Fixed failing test t3115 via judicious application of -Yfatal-warnings.
No review.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
make normalize slightly more aggressive in loading symbol info, while )
tolerating the righteous cycle (use sym.info.typeParameters instead )
of unsafeParams this is needed to make sure higher-kinded types have )
their type parameters (otherwise we'd get a PolyType with NoSymbol for )
typeParams )
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
- new immutable HashMap implementation based on a hash trie. this is the
first iteration, more optimizations will be added later. - updated test
cases to reflect new ordering of elements - made Map.empty and Set.empty
singletons, deprecating classes Map.EmptyMap and Set.EmptySet Review by
extempore, odersky.
|
|
|
|
|
|
| |
null, and thrown MatchErrors don't NPE trying to stringify null. No
review.
|
|
|
|
|
|
|
|
|
| |
Fix for #3136 by reverting the line in r18184 which caused this and
other regressions. The downside is that the #1697 test case no longer
passes, but protracted shrug because it wasn't entirely fixed anyway.
Review by moors. (Can you triangulate your way to a patch where both
work simultaneously? It's today's bonus challenge!)
|
| |
|
|
|
|
|
|
| |
ScalaRunTime method to perform sameElements as fix for #2867. Review by
odersky.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Added -Xmigration option and @migration annotation. At present it will
warn about the following changes from 2.7 to 2.8:
Stack iterator order reversed
mutable.Set.map returns a Set and thus discards duplicates
A case 'x @ Pattern' matches differently than 'Pattern'
Review by odersky.
|
| |
|
| |
|
| |
|
|
|
|
|
| |
trailing spaces in decompiled annotations are trimmed
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
what must be legacy scalatest.* properties to partest.*, boldly assuming
that the fact that partest is pretty much unusable outside of scalac
means there are no users outside of scalac who might be disrupted by
eliminating old property names. Review by community.
|
|
|
|
|
| |
specialized implementations.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Added ## method to Any as our scala hashCode method which provides
consistent answers for primitive types. And I'm sure we're all tired of
new starrs, but it's hard to add a method to Any without one. This patch
only brings ## into existence, but nothing calls it yet.
// some true assertions
scala> assert(5.5f.## == 5.5f.hashCode)
scala> assert(5.0f.## != 5.0f.hashCode && 5.0f.## == 5L.##)
No review. (Already reviewed by odersky.)
|
|
|
|
|
|
| |
Expanded the check from #1392 to enclose #3123 as well so that "case Int
=> " doesn't crash. Closes #3123. Review by odersky.
|
|
|
|
|
|
| |
Special cased an error message for the common situation of calling
AnyRef methods on Any or AnyVal. Review by odersky.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Quite a lot more work on XML equality than I can properly justify
spending time on, but you know how it is once you get started on
something. This commit will likely break some code out there in the
world but this is impossible to avoid if we are to achieve sane equality
in trunk.
For anyone who was relying upon the 2.7 equality behavior for
scala.xml.* classes, using "xml_==" instead of "==" for comparisons will
restore the old behavior. The standard == on xml elements now attempts
to behave in such a way that symmetry and hashCode contracts will be
preserved. It's probably not 100% there yet, but I can tell you this: it
is closer today than it was yesterday.
Review by community.
|
| |
|