| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| ... | |
| |
|
|
|
|
|
| |
that can arise when return types of public facing methods are inferred.
We eventually need some mechanism to make such issues easier to avoid.
No review.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Went ahead and implemented classpaths as described in email to
scala-internals on the theory that at this point I must know what I'm
doing.
** PUBLIC SERVICE ANNOUNCEMENT **
If your code of whatever kind stopped working with this commit (most
likely the error is something like "object scala not found") you can get
it working again with either of:
passing -usejavacp on the command line
set system property "scala.usejavacp" to "true"
Either of these will alert scala that you want the java application
classpath to be utilized by scala as well.
Review by community.
|
| |
|
|
|
|
|
|
| |
Noticed we still have a bunch of collection classes which are rather
lacking. Did some integration, added some companion objects. Not
thrilled with the overall picture in there, there's still a lot which
should be done. Updated a deprecation message, closes #3202. No review.
|
| |
|
|
|
|
|
| |
Seq-derived classes. Creating GrowingBuilder to complement AddingBuilder
on classes with += but not +. Fixed some inconsistencies I came across
in the process. No review.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
| |
During my last look at r21224 I noticed what must be a long standing
bug in Array.update handling. Fixing this probably never to be noticed
corner case (see bug3175.scala) seduced me into drumming out some
duplication. At least we got some nice commenting out of it. Review by
dubochet.
|
| |
|
|
|
|
|
|
|
|
| |
Some minor changes in scala.swing.* which I was glancing through because
of #3196. I noticed the Font object was in package scala instead of
scala.swing, which looks sure to be a mistake (an easy one to make, and
one others have made as well, because we're not entirely used to package
objects.) I didn't want to accidentally ship a scala.Font so I moved it
into swing. Review by imaier.
|
| |
|
|
|
|
|
| |
Some work on the Array methods as they manifest in refinement types:
tightening when Array code is generated and also what code is generated.
Review by dubochet.
|
| |
|
|
|
|
|
| |
Half-disabled productElementName until I have time to reimplement it
more to martin's liking. ("Half" because full disabling is not possible
until starr has forgotten about it.) No review.
|
| |
|
|
|
|
|
|
| |
Returning to the thrilling world of equality and hashCodes now
that Any.## is a reality. Moved the hash functions from Predef to
ScalaRunTime, and made what appears to be an optimization to equals by
not losing the result of an instanceof test. Review by community.
|
| |
|
|
|
| |
Added a tryToSetFromPropertyValue implementation for MultiStringSetting.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
to BufferLike (++ and similar now create a new collection.)
Removed MapLikeBase. Annotated all the methods in mutable.{ Map, Set }
which mutated in-place in 2.7 to note that they create new
collections, and implemented same.
At this point the only +/- like method which mutates in place which I am
aware of is BufferLike.+ (see source comment for my observations.)
Also tweaked some collections return types as necessitated by these
changes, such as mutable.Set.clone() now returning "This" rather than
mutable.Set[A].
References #3089, closes #3179. Review by odersky.
|
| | |
|
| |
|
|
|
|
| |
If people think some operations can be more lazy, please provide
patches/do changes. Also brought proxies and forwarders into line.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
Continuations support classes are included in scala-library.jar
so their sources should be in scala-library-src.jar. Also export
scala.util.continuations from the scala-library bundle.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
| |
Fixed build problem by eliminiating a redundant implicit in scalap.
Review by extempore.
|
| |
|
|
|
| |
Closes #2688 by disallowing call-by-name implicit parameters. No review.
|
| | |
|
| |
|
|
|
| |
different from the other errors, so no second try was done for them.)
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
| |
added support for continuations in try/catch blocks. review by
community.
|
| |
|
|
|
|
|
| |
Tracked down docs.lib build issue from the dentist's chair while waiting
for my teeth to numb. Checking in over open wireless access point. This
is dedication. No review.
|
| |
|
|
|
|
| |
fixed treatment of annotated types in isNumericSubType. re-enabled test
case. review by odersky
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
| |
Reverting a couple replacements from that last patch which don't look so
safe on re-examination. No review.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
| |
More support code for the big partest patch I'm working on to finally
finish classpaths for good. No review.
|
