| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
As part of https://github.com/lampepfl/dotty/issues/1589, use the
new error message for static super references where the qualifier
isn't a parent of the class.
Tested:
Added unit test.
|
|\
| |
| | |
Tailrec for derivesFrom/lookupRefined/classSymbol/classSymbols
|
| | |
|
|\ \
| | |
| | | |
Change "recursive/cyclic definitions needs type" errors to Message
|
| | |
| | |
| | |
| | | |
Fall-back to reporting "overloaded or recursive needs type".
|
| | |
| | |
| | |
| | |
| | |
| | | |
Split error messages for recursive method and overloaded method needs type into two (but
did not solve the analysis which to show).
Make CyclicReference type error construct corresponding error message.
|
| |/ |
|
| | |
|
| | |
|
|/
|
|
|
| |
(1) Drop unused error message
(2) Drop test which is now illegal
|
|\
| |
| | |
Change 'private, protected, or this expected' to Message
|
| | |
|
|/
|
|
|
| |
Previous import gave test errors under eclipse. Probably
due to some stray directory on the classpath.
|
|\
| |
| | |
Add overloading support for case-closures
|
| | |
|
|/ |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
* 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)
|
|
|
|
|
|
| |
* Change 'overrides nothing' to report via Message, split into two different messages
* Change 'overrides nothing' to report via Message, split into two different messages
|
| |
|
| |
|
| |
|
| |
|
|\
| |
| | |
Fix #1907: Improve error message
|
| | |
|
|/ |
|
|\
| |
| | |
Add sbt-based bootstrap
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The bug was that we declared case classes like:
case class CompFailed() extends NegTestState
but we used their companion objects like in:
case _ => CompFailed
Interestingly, this bug was caught by compiling this code with dotty,
instead of `failureStates` getting inferred to be of type `AnyRef`, it
ended up being a union of object types, this allows dotty to realize our
subsequent pattern match on `failureStates` cannot possibly succeed:
-- Error: /home/smarter/opt/dotty/compiler/test/dotty/partest/DPConsoleRunner.scala
353 | case CompFailedButWrongDiff() =>
| ^
| missing parameter type for parameter x$1 of expanded function x$1 =>
| x$1 @unchecked match
| {
| case CompFailedButWrongDiff() =>
| nextTestActionFailing(s"output differs")
| true
| case _ =>
| false
| }, expected = ?
-- Error: /home/smarter/opt/dotty/compiler/test/dotty/partest/DPConsoleRunner.scala
353 | case CompFailedButWrongDiff() =>
| ^^^^^^^^^^^^^^^^^^^^^^^^
|Pattern type CompFailedButWrongDiff is neither a subtype nor a supertype of selector type CompSucceeded | CompFailedButWrongNErr | CompFailed | CompFailedButWrongDiff'where: CompFailedButWrongDiff is a class in method runNegTest
| CompFailedButWrongDiff' is a object in method runNegTest
|
| | |
|
| |
| |
| |
| |
| | |
This is necessary to run the tests with the bootstrapped projects and is
just much better than hardcoding them anyway.
|
|/ |
|
|\
| |
| | |
Improve whitelist infrastructure.
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| | |
Now that that the blacklist is fully know
and is small enough, it will be simpler to
maintain only the blacklist.
|
| | |
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is useful for two reasons:
- All published Scala versions are of the form a.b.c and some tooling
expect that, like sbt CrossVersion API.
- Using 0.1.1 instead of 0.1.0 means that we match the version number of
dotty-sbt-bridge, this is simpler and means that in the future sbt
could automatically choose the correct version of dotty-sbt-bridge so
that the user does not need to specify scalaCompilerBridgeSource in
his build.sbt
Note: it's awful that we have hardcoded paths to jars and that I had to
change them, but I won't fix that now.
|
|
|
|
|
|
|
|
| |
The issue was that all the files stdlib files where
copied in partest-generated/pos/compileStdLib direclty
(i.e. directories flattend). This implies that files with
the same names would overwrite eachother (like `package.scala` and
`Set.scala`).
|
|
|
|
|
| |
Implicit modifiers were quite irregular compared
to the other ones. This commit does a cleanup.
|
| |
|
| |
|
|
|
|
|
| |
-verbose output was suppressed like all other non-error
output in the tests. Now we don't filter output if -verbose is set.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
sbt adds the correct jars to classpath and the tests depend on
`packageAll` which creates these. When using something else however,
these together with `sbt-interfaces` do not get propagated from the
build.
To remedy this and make the testing a bit more flexible, we now
take these from `sys.props` instead, see `tests/dotty/Jars.scala`.
If the props aren't defined we fall back to the ones default to sbt.
|