| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| ... | |
| | | |
|
| |/
|
|
|
|
|
|
|
| |
Implicit and non-implicit functions are incomparable with <:<, but are
treated as equivalent with `matches`. This means implicit and non-implicit
functions of the same types override each other, but RefChecks will
give an error because their types are not subtypes.
Also contains a test for #2002.
|
| | |
|
| |\
| |
| | |
Remove unused flags
|
| | | |
|
| |\ \
| | |
| | | |
Use enum for error messages IDs.
|
| | |/ |
|
| |/
|
|
| |
This is necessary if we ever want to get rid of our dependency on scala-compiler
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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 #1484: position of while incorrect in debug
|
| | | |
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| |
| | |
* 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
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| | |
`partest` and `partest-only` are now run through
`dotty-compiler-bootstrapped`. The old bootstrapping mechanism is
deleted since it has been unmaintained and broken for several months and
that I do not wish to maintain two bootstrapping mechanisms.
|
| | |
| |
| |
| |
| | |
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.
|
| | | |
|
| |\ \
| | |
| | | |
Fix benchmarks and add multiple mini benchmark tests
|
| | | | |
|
| | |/
|/|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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`).
|
| | |
| |
| |
| |
| | |
Need to be careful not to read a classfile before a compilation unit
defining the annotation is entered.
|
| | |
| |
| |
| |
| |
| | |
Fixing two failures in stdlib having to do with widening. In both
cases, a widenIfUnstable was required. One was widening too much,
the other too little.
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| | |
SystemProperties leads to a dottydoc failure, so stays blacklisted
for now. It does pass the normal compile-stdlib test.
|
| | | |
|
| | |
| |
| |
| |
| |
| | |
- Move non-specialized functions to whitelist
- Replace `macro ???` with just `???` in scala-scala
Several other consolidations
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| | |
When faced with a denotation that combines parameterless and nullary method
definitions (toString is a common example), ignore any redundant () applications.
|
| | | |
|
| | |
| |
| |
| | |
b960b12887331744c9ecaeedc90054fc2e313230)
|
