| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
| |
Previously, the following code accidentally used the implicit Context
parameter of `typedApply`:
tryEither {
implicit ctx => typedOpAssign
|
|
|
|
|
|
| |
The captured context was passed implicitly to dd.rhs, atGroupEnd is
always run with the same runId as the captured context so this should be okay,
but it's better to avoid using two contexts in the same expression anyway.
|
|
|
|
|
| |
The capture context was only used to get its phase so shouldn't cause
any problem.
|
|\
| |
| | |
Disable tests that require scala-compiler
|
| |
| |
| |
| | |
This is necessary if we ever want to get rid of our dependency on scala-compiler
|
|\ \
| | |
| | | |
TreeMap/TreeAccumulator: proper context for inlined trees
|
| | |
| | |
| | |
| | |
| | |
| | | |
This was already be done in TreeTraverser but should also be done in
TreeMap and TreeAccumulator for ctx.error(..., tree.pos) to not use
completely incorrect positions inside inlined trees.
|
|\ \ \
| | | |
| | | | |
checkNoPrivateLeaks: Use correct position for errors
|
| | |/
| |/|
| | |
| | |
| | |
| | |
| | | |
Previously we never used the `pos` argument of `checkNoPrivateLeaks` and
instead used `sym.pos`, this makes a difference for calls to
`avoidPrivateLeaks` coming from `TreeUnpickler` where we should use
`tree.pos` instead.
|
|\ \ \
| | | |
| | | | |
Fix #1991: Use classtag where available in unapply
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
We cannot assume that the untyped rhs of the bind is a `Typed` tree,
with extractors it might be an `Apply` node, and in general it might
also be a `Parens` node.
|
| |/ / |
|
|\ \ \
| |/ /
|/| | |
Bootstrapped dotty should not depend on non-bootstrapped dotty-library
|
|/ / |
|
|\ \
| | |
| | | |
Factor out logic for scala functions.
|
| |/
| |
| |
| |
| |
| |
| |
| | |
* Add `isSyntheticFunction` checks for synthetic functions such as FuntionN
for N > 22 and ImplicitFunctionN for N >= 0.
* Add `erasedFunctionClass` to get the erased verion of synthetic functions.
* Change the semantics of `isFunctionClass` to return true if it is any kind of
FunctionN or ImplicitFunctionN.
|
|\ \
| | |
| | | |
Change '... expected but found ...' to Message
|
|/ / |
|
| |
| |
| |
| |
| |
| | |
This is a gross hack to support the need for a $scope
binding when XML literals are created. It should go away
once we phase out XML literals. A library-based
solution should use implicits instead.
|
|\ \
| | |
| | | |
Fix #1975: Align valdefs and for expressions for patterns
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
val definitions and for expressions both distinguish whether
something is a pattern or a variable binding. They no do it
the same way: `ident` or an `ident: type` is a variable binding,
everything else is a pattern. Previously, capitalized idents
were considered as bindings in valdefs but as pattern in fors.
|
| | |
| | |
| | |
| | | |
The non-determinism is anonying, disable for now until we
have a better solution.
|
|\ \ \
| |/ /
|/| | |
increase command wait time to 1s
|
|/ /
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This change helps to reduce non-determinism in the test. The problem
can happen when two consecute commands interfere:
[expect] [jdb]
cmd1 ---->
sleep 0.5 <--- part 1 of rep1
read & match buffer
clear buffer
cmd2 ---->
<--- part 2 of rep1
|
|/
|
|
|
|
|
|
|
|
| |
* Change 'forward reference extending over the definition' to Message
* Change 'forward reference extending over the definition' to Message
* pesky file should not be included
* Change 'forward reference extending over the definition' to Message (test case)
|
|\
| |
| | |
Fix #1501 - Check trait inheritance condition
|
| |
| |
| |
| | |
It's java.io, not java.lang.
|
| |
| |
| |
| |
| | |
Excepted are only Serializable and Comparable. This follows
scalac's behavior.
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The leading class should be the superclass of the first trait
(which is not always Object).
We could think of a more refined condition, (i.e. taking the least
common superclass of all extended traits), but I think it's not worth
it, as one can always spell out the right superclass manually.
|
| |
| |
| |
| |
| |
| |
| |
| | |
Need to take account of situations like
extends Any with java.io.Serializable
which occur in stdlib.
|
| |
| |
| |
| |
| | |
We need to check a coherence condition between the superclass
of a trait and the superclass of an inheriting class or trait.
|
|\ \
| | |
| | | |
fix #1484: position of while incorrect in debug
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
|\ \ \
| | | |
| | | | |
Fix parsing annotation on function type
|
| | | | |
|
|\ \ \ \
| | | | |
| | | | | |
add dotty-bot
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|