| Commit message (Collapse) | Author | Age | Files | Lines |
|\
| |
| | |
SI-6559 Fix raw string interpolator: string parts which were after the first argument were still escaped
|
| |
| |
| |
| |
| | |
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.
|
| |
| |
| |
| | |
argument were still escaped
|
|\ \
| | |
| | | |
SI-6648 copyAttrs must preserve TypeTree#wasEmpty
|
| |/
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This field tracks whether the type is an inferred
on, subject to removal in `resetAttrs`, or an explicit
type, which must remain.
In ae5ff662, `ResetAttrs` was modified to duplicate
trees, rather than mutate trees in place. But the
tree copier didn't pass `wasEmpty` on to the new tree,
which in turn meant that the subsequent typing run
on the tree would not re-infer the types. If the
type refers to a local class, e.g. the anonymous
function in the enclosed test case, the reference
to the old symbol would persist.
This commit overrides `copyAttrs` in TypeTree to
copy `wasEmpty`.
We might consider representing this as a tree
attachment, but this would need to be validated
for the performance impact.
|
|\ \
| | |
| | | |
SI-6661 - Remove obsolete implicit parameter of scala.concurrent.promise method
|
| |/
| |
| |
| |
| |
| |
| |
| | |
Clarification of @heathermiller:
This is an inconsistency introduced after refactoring implicit ExecutionContexts.
In commit 1dfce90246f7d334 the implicit ExecutionContexts were removed from everything else in Promise.scala,
but it appears that method promise was missed in the scala.concurrent package object, which would've made
sense to remove back then.
|
|\ \
| | |
| | | |
SI-6644 Account for varargs in extmethod forwarder
|
| |/
| |
| |
| |
| | |
Which sounded difficult, so instead I offshored the work
to the friendly republic of TreeGen.
|
|\ \
| | |
| | | |
Update tools/epfl-publish
|
| |/
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Currently, during each Scala nightly build, the epfl-publish script rsyncs the resulting dists/archives to the repository machine (chara).
Now, as a result of a change introduced a while back, dists/archives/ now also contains a symbolic link, created at the end of the build when the targets "pack-archives.latest.*" are invoked (in src/build/pack.xml). That was introduced in:
scala/scala@506bcfe71c93160ebfa0ca9b8b170b4b54e844e9
scala/scala@cb99853c8655686dae1288cbcd44a42cf1ea6609
This link, created in dists/archives/, is copied over as-is at the end of the rsync to chara by epfl-publish. On chara, however, the link points to an invalid target (the path is absolute).
Separately, the repository directory on chara is rsync'd every 30 minutes over to the machine that serves www.scala-lang.org, via cron. Rsynch finds that the link target does not exist, and generates an email with the crontab log, which is then duly sent to a system mailbox. Every 30 minutes. Since March. Needless to say, the mailbox is pretty large by now.
The fix is trivial, but this needs to be included in all the branches that are tested during the nightly. Since RC2 has just been cut, and the code frozen, I'm not sure how this change can be included without disruption; therefore, I'll just send a pull request on 2.10.0-wip, and let Josh/Paul take the appropriate steps.
|
|\ \
| |/
|/| |
SI-6646 Fix regression in for desugaring.
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The previous commit regressed in these cases:
// no withFilter
for (X <- List("A single ident is always a pattern")) println(X)
for (`x` <- List("A single ident is always a pattern")) println(`x`)
At the top level of the LHS of a <-, such identifiers represent
new bindings, not stable identifier patterns.
|
|/
|
|
|
|
| |
The early check in the parser of pattern irrefutability,
added in c82ecab, failed to consider InitCaps and
`backquoted` identifiers.
|
|\
| |
| | |
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.
|
|\ \ \
| |/ /
|/| | |
SI-6575 Plug inference leak of AbstractPartialFunction
|