| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| | |\ \ \
| | | |/ /
| | |/| /
| | | |/ |
|
| | | |\
| | | | |
| | | | | |
Fixing issue where OSGi bundles weren't getting used for distribution.
|
| | | | | |
|
| | | |\ \
| | | | | |
| | | | | | |
Fixes example in Type.asSeenFrom
|
| | | | |/
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
It was written in some form of non-executable pseudo-code before and
that might be quite confusing for people who are not familiar with scala
reflection.
|
| | | |\ \
| | | | |/
| | | |/| |
Updated copyright dates throughout compiler and stdlib for upcoming release
|
| | | | |
| | | | |
| | | | |
| | | | | |
2013
|
| | | | | |
|
| | | |\ \
| | | | | |
| | | | | | |
Fix for SI-6600, regression with ScalaNumber.
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Not much in the end; I divided ScalaNumericConversions
into two traits such that the ScalaNumericAnyConversions can
be used in value classes, and ScalaNumericConversions can
override methods in ScalaNumber (since one trait cannot do
both those things.)
The fact that ScalaNumber is privileged for equality but a) extends
java.lang.Number and therefore b) cannot be a value class is something
we will want to revisit real soon.
|
| | | |\ \ \
| | | | |/ /
| | | |/| | |
SI-6562 Fix crash with class nested in @inline method
|
| | | |/ /
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
e6b4204604 moved access widenings from ExplicitOuter to
SuperAccessors to reflect them in pickled signatures so
that the inliner can take advantage of them under separate
compilation.
The followup discussion [1] determined that this wasn't
the right solution: while it enabled new separate compilation
inlinings, it failed to widen access of outer pointers and
hence prevented certain inlinings.
A better solution was proposed: modify the inliner to know
that access widening is guaranteed to have happened in
ExplicitOuter for any field accessed by an @inline-d method
body, rather than relying solely on the pickled types.
But this hasn't happened yet. In the meantime 07f94297 / #1121
reinstated the access widening to SuperAccessors, but took a
slightly different approach, using `Symbol#enclMethod` rather
than `closestEnclMethod`. That deviation triggers SI-6562.
This commit goes back to `closestEnclMethod`.
[1] https://groups.google.com/forum/#!topic/scala-internals/iPkMCygzws4
|
| | | |\ \
| | | | |/
| | | |/| |
API docs: reflection fixes, AnyVal/Any documentation additions, errata
|
| | | | | |
|
| | | | | |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
- Added the labels across scala.reflect and scala.reflect.macros
- Added the styling in template.css that is used by all labels
|
| | | | | |
|
| | | | |
| | | | |
| | | | |
| | | | | |
reflection.internal). It probably needs more cleanup of the api wrt to ranges etc but let's leave it for later
|
| | | |/
| | | |
| | | |
| | | |
| | | | |
- Updates AnyVal docs to address value classes.
- Updates Any docs to address universal traits.
|
| | | |\
| | | | |
| | | | | |
New take on SI-6534, value classes.
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Only exclude hashCode and equals from being overridden in
value classes, not other synthetics which may turn up such
as case class methods.
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Don't prohibit equals and hashCode in universal traits;
instead, always override them in value classes.
|
| | | |\ \
| | | | | |
| | | | | | |
Fixes SI-6500 by making erasure more regular.
|
| | | | |/
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
With the introduction of value classes, erasure uses specialErasure where a value class C with underlying type T is unboxed to an ErasedValueType. ErasedValue types are eliminated on phase later, in post-erasure. This was done everywhere, except in the parameter types of bridge methods. That was a mistale, because that way bridge methods could not do the boxing/unboxing logic triggered by ErasedValueTypes.
Note: there is one remaining use of erasure (not specialErasure) in Erasure.scala. I put in a comment why that is OK.
|
| | | |\ \
| | | | | |
| | | | | | |
SI-6556 no assert for surprising ctor result type
|
| | | | |/
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Previous fix to value classes uncovered some questionable cases in the backend where result types of constructor signatures are surprising. It's not a big deal because these types will be ignored afterwards anyway. But
the method uncovered some questionable situations which we should follow up on. However, breaking 2.9 code because of this is way too harsh. That's why the asserts were converted to warnings.
review by @paulp, @adriaanm
|
| | | |\ \
| | | | | |
| | | | | | |
SI-6577 Make actors-migration an external module
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
* Removes actors-migration hooks from partest
* Removes actors-migration code
* removes actors-migration tests
* removes actors-migration distribution packaging.
|
| | | | |\ \
| | | | |/ /
| | | |/| | |
|
| | | |\ \ \
| | | | | | |
| | | | | | | |
SI-6578 Harden against synthetics being added more than once.
|
| | | | | |/
| | | | |/|
| | | | | |
| | | | | |
| | | | | | |
Don't add synthetic methods if they already contain synthetic
methods from the set we're about to add.
|
| | | |\ \ \
| | | | | | |
| | | | | | | |
SI-6581 fixed by inlining `Actor.self`.
|
| | | | |/ /
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
This avoids the necessary type cast that was preventing leakage of internal migration classes.
Review by @phaller
|
| | | |\ \ \
| | | | | | |
| | | | | | | |
Fixes SI-5031 for separate compilation scenario.
|
| | | | |/ /
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
When you have a conflicting member in package object and normal package that share the same namespace we remove the latter ClassSymbol from the scope. Now, this has an unpleasant consequence that companionClass/companionModule/companionSymbol no longer work correctly as they rely on finding the correspondent symbol using decls of the owner.
This fixes the problem of SI-5031 for separate compilation. Why the above change matters for finding foo.bar.Foo? Because when parsing the class we needed information about the static module (and we have the correct module symbol when completing the info). It's just that 043ce6d0565c9d5d960 relied on no longer valid assumptions. So we were getting NoSymbol and sym.exist was failing.
Obviously a more complete solution would be better if we didn't rely on the scope but that's too big to change for 2.10.0.
|
| | | | |/
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
* Removes actors-migration hooks from partest
* Removes actors-migration code
* removes actors-migration tests
* removes actors-migration distribution packaging.
|
| | |\ \ \
| | | | | |
| | | | | | |
Fix for SI-6597, implicit case class crasher.
|
| | |/ / /
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
It seems to me like every call to scope.lookup in the
compiler is a latent bug. If a symbol is overloaded, you
get one at random. (See the FIXME comment in f5c336d5660
for more on this.)
|
| | |\ \ \
| | | | | |
| | | | | | |
Merge 2.10.0-wip into 2.10.x.
|
| | |\ \ \ \
| | | | | | |
| | | | | | | |
SI-6488: Fix for race with open I/O fds
|
| | | | | | | |
|
| | |\ \ \ \ \
| | | |/ / / /
| | |/| | | | |
Fixes SI-6559 - StringContext not using passed in escape function.
|
| | |/ / / /
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
As reported by Curtis Stanford, with indication of what to fix. standardInterpolator was not correctly
calling the passed in process function, so raw strings were not really raw.
|
|\ \ \ \ \ \
| | | | | | |
| | | | | | | |
Ticket/revert primitive array opt
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
This reverts commit 8265175ecc42293997d59049f430396c77a2b891.
|
|/ / / / / /
| | | | | |
| | | | | |
| | | | | | |
This reverts commit 092345a24c22a821204fb358d33272ae8f7353be.
|
|\ \ \ \ \ \
| |/ / / / /
|/| | | | | |
SI-6611 Tighten up an unsafe array optimization
|
| | | | | | |
|
| | | | | | |
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
The net was cast too wide and was unsafely optimizing away array
copies.
|