| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| ... | |
| | | | | | | |
|
| | | | | | | |
|
| | |/ / / / |
|
| |\ \ \ \ \
| | | | | |
| | | | | | |
More robust findScalaHome in bash scripts
|
| | |/ / / /
| | | | |
| | | | |
| | | | |
| | | | | |
Allows multiple absolute or relative symlinks by jumping through
the directories while following the links.
|
| |\ \ \ \ \
| | | | | |
| | | | | | |
Made parser less hostile to inspection.
|
| | | |/ / /
| |/| | |
| | | | |
| | | | | |
By annotating all the boolean method arguments.
|
| |/ / / / |
|
| |\ \ \ \
| | | | |
| | | | | |
allows printing .icode files after any optimiz phase
|
| | |/ / / |
|
| |/ / / |
|
| |\ \ \
| |/ /
|/| | |
Partial redesign of incremental compiler invalidation.
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
We now do the right thing when packages are either newly created or deleted. Previously there was a problem when a new package was created inside a system package (and, unofrtunately, root is a system package). That's fixed now. We also approximate more tightly now when packages are newly created (iei the newly created symbol gets rescanned, instead of its owner).
Incremental class invalidation: dealing with empty package.
The compiler can now also invalidate the empty package. Previously, no invalidation was done because empty was identified with root, which is considered a system package.
(1) Fixed NPE when creating a new toplevel package in invalidation. (2) generalized interface to deal with multiple entries at a time.
|
| |\ \ \
| |/ /
|/| | |
fix t5843
|
| | | | |
|
| |\ \ \
| | | |
| | | | |
Implemented functionality to invalidate classpath entries
|
| | | | |
| | | |
| | | |
| | | | |
incremental compiles.
|
| |\ \ \ \
| | | | |
| | | | | |
SI-5845 Advances the example from a crasher to an inference failure.
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
The inference failure itself seems like an instance of of SI-3346.
But dependent method types (which triggered the crash), can be employed
to avoid inferring the type constructor CC.
class Num[T] {
def mkOps = new Ops
class Ops { def +++(rhs: T) = () }
}
class A {
implicit def infixOps[T](lhs: T)(implicit num: Num[T]): num.Ops = num.mkOps
implicit val n1: Num[Int] = new Num[Int] { }
5 +++ 5
}
|
| |\ \ \ \ \
| |_|_|/ /
|/| | | | |
fixes for exhaustivity
|
| | | | | | |
|
| | |/ / / |
|
| |\ \ \ \
| |/ / /
|/| | | |
Fix a NSDNHAO in extension methods.
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
A bridge method, created when we override a method from
a superclass and refine the return type, was appearing
as an overloaded alternative. (`erasure` doesn't create
new scopes, so the bridges it builds are visible at
earlier phases.)
The problem was masked when compiling with specialization,
which *does* create a new scope, shielding the code in
question from the artefacts of erasure.
To fix the problem, we filter out bridge methods from
the overloaded alternatives returned by `.decl`, as would
happen internally in `.member`.
|
| | | | |
| | | |
| | | |
| | | | |
Who could have suspected it would actually be right most of the time?
|
| |/ / /
| | |
| | |
| | | |
...be a little less chatty.
|
| |\ \ \
| | | |
| | | | |
fix SI-5829: refinement typeref has a prefix
|
| | |/ / |
|
| |\ \ \
| | | |
| | | | |
SI-5318 Make implicit divergence checking PolyType aware.
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Replaces the two active subclasses of `SymCollector` with
direct use of traversal methods of `Type`.
Wildcard free class type parameters, not just method type parameters,
when stripping the core type of candidate implicits. The spec doesn't
make any such distinction, and the enclosed test, t5318c, crashes
without this change.
|
| |\ \ \ \
| | | | |
| | | | | |
Cleaning up some code introduced for the old presentation compiler long ...
|
| | | | | |
| | | | |
| | | | |
| | | | | |
ago. Review by @dragos
|
| |\ \ \ \ \
| | | | | |
| | | | | | |
Closes SI-5821.
|
| | |/ / / /
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
This was an interesting one. Basically an erroneous
import was creating an erroneous symbol for Array (similary
for other symbols that were 'found' in this import) which was
leading to all sorts of inconsistencies and spurious errors.
This wasn't a bug in ContextErrors but rather something that
existed for ages and was hidden from the general audience.
Review by @paulp.
|
| |\ \ \ \ \
| | | | | |
| | | | | | |
Fixes SI-5085 and SI-4833.
|
| | | |_|/ /
| |/| | | |
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
we don't handle switches with guards, whereas the old patmat did
to ease the transition, let's not error out and see how we can resolve this
|
| |\ \ \ \ \
| | | | | |
| | | | | | |
Fixes SI-5805
|
| | |/ / / / |
|
| |\ \ \ \ \
| | | | | |
| | | | | | |
Fixes SI-5428.
|
| | |/ / / / |
|
| |\ \ \ \ \
| | | | | |
| | | | | | |
Move implicit ExecutionContext to be determined by lexical scope
|
| | |/ / / /
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Port of a pull request originally submitted by @havocp.
- declare the invariant that all app callbacks have an
associated ExecutionContext provided at the place
the callback is passed to a method on Future
- always run callbacks in their associated EC
- since all callbacks have their own EC, Promise
does not need one
- "internal" callbacks don't need to defer execution either
since we know the ultimate app callback will do so,
therefore we can use an immediate executor for these
|
| |/ / / / |
|
| | | | | |
|
| |\ \ \ \ |
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
We were getting away with this somehow, but the types are wrong after
typer and that sort of thing is noticed by more people now. I took the
opportunity to add our first -Ycheck:all test, which is at least as much
about helping -Ycheck:all remain in good working order as it is about
this test.
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
