| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
It fails without any test output in partest
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
* Fix varargs in methods (Issue: #1625)
* Fix minor comments
* Change varargs parameter message
* Fix failed test, fix case for constructor
|
| |
|
|
|
| |
This fix is inspired by 6c91684, but I couldn't tell you why it works
exactly, it's just something I tried.
|
| |
|
|
|
|
|
| |
Before this commit, ParSetLike compiled fine as part of compileStdLib
but crashed when compiled by itself because we tried to force a LazyRef
while forcing the same LazyRef. This commit fixes this by being slightly
more lazy where it matters.
|
| |
|
|
|
| |
These two directories were tested using the same flags, but tests/tasty
compiled all of its files at once which is usually not what is intended.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
| |
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
|
| | | |
|
| |/
|
|
| |
This is necessary if we ever want to get rid of our dependency on scala-compiler
|
| | |
|
| |\
| |
| | |
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.
|
| | |
| |
| |
| |
| | |
This way we can test that dotty compiles dotty using
dotty-compiler/test-only -- --tests=dotty
|
| | |
| |
| |
| |
| | |
This was broken in 06a3d47ea9fd1b67b3acba9d115a16d18549e377 when the
-deep argument was removed
|
| | | |
|
| |/
|
|
|
|
|
|
|
|
|
|
| |
1. I noted java_all was not running(it took 0.01s to complete); fixed by
changing the test directory.
2. We suspected tasty_bootstrap was gettng the wrong classpath and
had a lot of problems getting it to print the classpatg. Fixed
by refactoring the options we pass to tasty_bootstrap (it has
to be -verbose in addition to -classpath). For the moment,
both a turned off but we have to just swap a false to a true
to turn them on together.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| | |
|
| |
|
