| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
They are sorted according to the nesting depth of the classes they
represent. This is no necessarily the same as the nesting level of
the symbols of the proxy classes. i1990a.scala shows an example where
the two differ.
|
|
|
|
|
|
|
| |
Interesting that the tests pass even if we always assume outOfContext = true.
So this raises the question why have a flag? It's just that I am not sure the
`outOfContext` behavior is correct in all cases. So I prefer to be conservative
here.
|
|
|
|
|
| |
This shows that the builder pattern can be expressed
with implicit function types.
|
|
|
|
|
|
|
|
|
|
| |
The new situation in the test was that outer of the inlined method
was `A` but it's as seen from type is a subtype `B`.
We need two fixes:
- Ignore outerSelects in TreeChecker. These are treated as having fixed symbols.
- Adapt the outer-path logic to deal with code that's moved to another context.
|
|\
| |
| | |
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
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
|/ / / /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This PR will add a bot whose first purpose is to check the CLA of
contributing PRs. It improves on the old bot in that it checks each
commit individually, and doesn't get upset about 100+ commits.
It would be fun to do this PR with you @OlivierBlanvillain, feel free
to provide feedback/comments and refactor as you like
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
* Change 'overrides nothing' to report via Message, split into two different messages
* Change 'overrides nothing' to report via Message, split into two different messages
|
|\ \ \ \
| |_|/ /
|/| | | |
Support expecting compiler errors from all phases
|
|/ / / |
|
|\ \ \
| | | |
| | | | |
Fix dotr/dotc scripts
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|