| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| |\ \ |
|
| | | |
| | |
| | |
| | |
| | |
| | | |
They were sneaking through as polymorphic Arrays and avoiding boxing.
Closes SI-4216
|
| | |/ |
|
| |\ \
| |/
|/|
| |
| | |
Conflicts:
src/library/scala/util/parsing/combinator/Parsers.scala
|
| | |
| |
| |
| | |
Also fixes potential issue with Parsers.phrase not being reentrant; however, I was unable to actually reproduce this issue in practice. (The order in which lastNoSuccess was being set and compared seemed to guarantee that it would never actually be a problem).
|
| | |
| |
| |
| | |
Oh boy, a checkfile! This is the best christmas ever!
|
| | |
| |
| |
| | |
Since the optimizer seems to have lost its mind.
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| | |
I guess we can look forward to more and more duplication in the
collections. I had to cut and paste the doc comment too, or at least
I have no idea how to avoid that given the file I took it from was in
parallel somewhere.
|
| | |
| |
| |
| | |
Your know, for performance. Closes SI-5641.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This change should be transparent to anything using sourceFile,
unless it was drinking from the inheritance well too deeply. Rather
than squander the already allocated field for every ClassSymbol not
being compiled from source, I'm now populating it with the file
representing the class. This will make a broad range of things easier,
like debugging, issuing useful error messages, symbol invalidation,
signature verification, you name it.
def sourceFile - still returns only source code files
def binaryFile - returns only class files
def associatedFile - returns whatever is there, if anything
Performance: I may be mistaken, but I believe this is a zero-impact
change. No new fields are allocated; fields which were null now hold
a useful reference. The reference is to a file instance which was
already being allocated and already long-lived.
Compare error messages:
// Version 1
% scalac a.scala
error: type _$1 is defined twice
// Version 2
% scalac a.scala
error: type _$1 is defined twice
conflicting symbols both originated in file './foo/package.class'
Note: this may be due to a bug in the compiler involving wildcards in package objects
one error found
Bonus for people who read commit logs. Try this in the repl
after starting power mode.
ListClass.info.members groupBy (_.associatedFile) foreach {
case (k, vs) => println("%s\n %s\n".format(k, vs map (_.defString) mkString "\n "))
}
|
| | |
| |
| |
| |
| |
| |
| | |
Now neg tests are treated like all the other tests in terms
of grouping, so if you have a negative test which requires more
than one pass (like the one enclosed with the next commit) you
can actually test it.
|
| | | | |
| | \ | |
| | \ | |
| | \ | |
| | \ | |
| | \ | |
| | \ | |
| | \ | |
| |\ \ \ \ \ \
| | | | | | |
| | | | | | |
| | | | | | | |
'refs/pull/474/head'; commit 'refs/pull/475/head'; commit 'refs/pull/476/head' into develop
|
| | | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
The acceptIf and acceptMatch parsers now check for end of input.
Review by moors.
|
| | | | | |/ / |
|
| | | | |/ / |
|
| | | |/ / |
|
| | |/ /
| | |
| | |
| | | |
Methods keySet, values and withDefault now return serializable collections.
|
| |\ \ \
| | | |
| | | | |
run patmat after typer, but not *right* after
|
| |/ / /
| | |
| | |
| | | |
sbt needs that spot right after type for its phase xsbt-api
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Closes SI-963, since it was one of my random 30 it won the prize.
The trick after adding the stability check (which has been sitting
there commented out for 3+ years) was that implicit search depended
on the wrongness, because memberWildcardType would create scopes
with members of the form
?{ val name: tp }
And since a def shouldn't match that, fixing it broke everything
until I flipped it around: memberWildcardType should be seeking
?{ def name: tp }
It could also search for a mutable value: the relevant quality
is that it not be stable so it doesn't have a tighter type than
the members it hopes to match.
|
| |/ /
| |
| |
| |
| | |
Don't change the owner of a return if the new owner is nested
inside the old owner. Closes SI-5612.
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
New this week, on SCALA.
Implicit class: "Spin me up an implicit method with my name."
Value class: "I need a companion object, pronto."
Narrator: "All was well with this arrangement... UNTIL."
What happens when these two wacky SIPs get together in the very
same class? You'll laugh until, eventually, you cry! Weeknights
at 9:30pm, only on SCALA.
Closes SI-5667.
|
| | |
| |
| |
| |
| |
| | |
Removed JacoMetaATTR.
Removed MetaParser.
|
| | | |
|
| | |
| |
| |
| | |
Through the oracle of pos/t1279a.scala.
|
| | |
| |
| |
| |
| |
| | |
Don't let inaccessible methods prevent calls to *Dynamic,
otherwise we are at the mercy of every "private" alteration
in every class we inherit. Closes SI-5040.
|
| | |
| |
| |
| |
| |
| |
| |
| | |
Most are pattern matcher bugs fixed by virtpatmat. A few are reifier,
package object, or miscellaneous. I threw in an original test for
SI-2337, to go with those for SI-1697, SI-3705, SI-4415, and SI-1357,
all of which (in the interests of making sure this basket has all the
eggs) I am closing.
|
| | |
| |
| |
| |
| |
| |
| | |
And for a bunch of other tickets where we unleash a stack
trace rather than printing a sensible error message. But
SI-3718 is a continuations plugin crash, now a reasonable
if somewhat vague error.
|
| | | |
|
| | |
| |
| |
| |
| |
| | |
Anyone who doubts the importance of avoiding duplication is
invited to look closely at the cause of this bug as revealed in
this one line patch.
|
| | |
| |
| |
| |
| | |
Still some issues with the repl namespace, which should
be managed in a first class way, not defensively/reactively.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
In favor of a marker attachment using Attachment, as suggested in
comments. (The Attachment interface needs work.) I did this bit trying
to fix SI-5715, but it's still a bit elusive because the Ident node is
thrown away as soon as there's a member definition.
Also, as far as I can see this will if anything propagate the
backquotedness of an identifier less effectively than before, because
TreeCopiers don't copy attachments. Maybe that's on the "todo" list? The
whole idea seems to depend on their being propagated to copies.
|
| | |
| |
| |
| | |
Closes SI-5728.
|
| | |
| |
| |
| |
| |
| | |
Eventually "-Xlint would have told you not to do that" will
be a catchphrase, like "I love it when a plan comes together"
or "respect mah authoritah."
|
| | | | |
| | \ | |
| | \ | |
| | \ | |
| |\ \ \ \
| | | | |
| | | | |
| | | | | |
'refs/pull/469/head'; commit 'refs/pull/470/head' into develop
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
If a package have a package object, generate the package's "linearization"
from the object.
|
| | | |/ /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
to improve Array[T] java-interop with T[],
normalize Object with Object{} to Object
fix #SI-5688 by flattening refined types in parents
updated check files to reflect flattening of refined types and updated position for refined types
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
Frobbed knobs and made little traits until all relevant
looking reflective calls were gone.
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Suggested by Simon in
https://groups.google.com/forum/?hl=en&fromgroups#!topic/scala-internals/z7s1CCRCz74
Now it eliminates backticks and gracefully bails out with an error
message when it can't remove the wiki syntax.
|
| | | |\ \ |
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
This patch is really by Lanny Ripple <lanny@spotinfluence.com>,
but I reworked it because I didn't want to put any more methods
onto String. Instead, there is a method on Regex which removes
the anchoring quality.
"""\d\d'"".r.unanchored
|
| | | |\ \ \
| | | |/ /
| | |/| | |
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
This patch fixes the motivating bug by detecting when a method is
the default arg getter for a constructor parameter. That requires
fixing a secondary bug where an arbitrary string was used to encode
<init> in lieu of <init>.encode. There is no speculative mangling.
|
| | | | |\ \
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Reverts name unenmanglement that was objectionable in the previous patch
commit 47bfd744177121de08fed489a5b0b1b59a1ae06a.
|
| | | | | | | |
|
| | | | | | | | |
| | | | \ \ \ | |
| | | | \ \ \ | |
| | | | \ \ \ | |
| | | | \ \ \ | |
| | | | \ \ \ | |
| | | | \ \ \ | |
| | | | \ \ \ | |
| | | |\ \ \ \ \ \ \ \
| | | | | | | | | | |
| | | | | | | | | | |
| | | | | | | | | | | |
'refs/pull/459/head'; commit 'refs/pull/460/head'; commit 'refs/pull/461/head'; commit 'refs/pull/462/head'; commit 'refs/pull/463/head'; commit 'refs/pull/464/head'; commit 'refs/pull/465/head' into develop
|
