| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
most notably Scala 2.13.0-M3
|
| |
|
|\
| |
| | |
fix Scala version number handling for 2.13 community build
|
|/
|
|
|
| |
we need to handle a Scala version like `2.13.0-pre-5e84129`,
as we see in nightly builds before bincompat is locked down
|
|\
| |
| | |
Avoid NPE with import trees
|
|/ |
|
|\
| |
| | |
Fix more corner cases in late expansion
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
e.g `val x2 = Foo[$1] with Bar = boundValue`
is rewritten to `val x2 = (Foo[$1] @uncheckedBounds) with Bar = boundValue`
This is to have refchecks turn a blind eye to the type argument that
doesn't conform the to type parameter bounds.
For regular compilation, without the async transform between patmat
and refchecks, bound conformance is disabled with:
https://github.com/scala/scala/blob/v2.11.7/src/compiler/scala/tools/nsc/typechecker/RefChecks.scala#L1743
Using the `uncheckedBounds` annotation is a newer, more inclusive way
of acheiving the same thing:
https://github.com/scala/scala/blob/v2.11.7/src/compiler/scala/tools/nsc/typechecker/RefChecks.scala#L1677
|
| | |
|
|\ \
| | |
| | | |
Travis makes us work harder now to actually get OpenJDK 6
|
| |/
| |
| |
| |
| | |
as per:
https://github.com/travis-ci/travis-ci/issues/8199#issuecomment-327246053
|
|\ \
| |/
|/| |
Some fixes and better uniformity in README.md.
|
|/ |
|
|\
| |
| | |
Fix decision about whether to use a trait or class as the parent
|
| | |
|
| | |
|
| | |
|
|\ \
| |/
|/| |
Fix ANF transform for corner case in late transforms
|
|/
|
|
|
| |
Unfortunately I wasn't able to extract a test case, but the patch
has been tested to fix a problem on a real world code base.
|
|\
| |
| | |
Improve generated code and flexibility
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
If a state does nothing but unconditionally transition to the
next state, remove it and rewrite predecessors to directly jump
to the successor state (or to the first non-dead successor.)
While we're doing this, compact the remaining state IDs to be
contiguous, which will allow use of a tableswitch in bytecode.
Sample bytecode demonstrating a tableswitch:
https://gist.github.com/retronym/6880c35b501fc1c91bed7f30c0f2c045
|
| | |
|
| | |
|
|/ |
|
|\
| |
| | |
support Scala 2.13.0-M2
|
|/
|
|
|
|
|
|
| |
and also move from 2.12.2 -> 2.12.3, just because
and sbt 0.13.15 -> 0.13.16, also just because
and scala-sbt-module 1.0.8 -> 1.0.12, because guess why
|
|\
| |
| | |
Reduce logging overhead and minor cleanups
|
|/ |
|
| |
|
|\
| |
| | |
Use scala-module-plugin, update tag-based publishing
|
|/
|
|
|
|
|
| |
The build didn't use the `scala-module-plugin` before but duplicated
most of its settings - maybe I missed the reason why this is the case?
Also update tag-based publishing to the latest version.
|
|\
| |
| | |
Typo
|
|/ |
|
|\
| |
| | |
In tests use tmp dir working on all operating systems
|
|/
|
|
| |
After this change tests pass also on Windows.
|
|\
| |
| | |
Bump to new snapshot version
|
|/ |
|
|\
| |
| | |
Bump to Scala 2.12.0
|
|/ |
|
|\
| |
| | |
Bump Scala version to 2.12.0-RC2
|
|/ |
|
| |
|
|\
| |
| | |
Rework build logic to determine which JDK use for release build
|
| | |
|
|\ \
| | |
| | | |
Add dependency information for including in project.
|
| | |
| | |
| | |
| | | |
Added dependency information for Maven and SBT so that it is easier for the developers who are new to the library.
|
|\ \ \
| | |/
| |/| |
Compatibility with Scala 2.12.0-RC1
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
- method local lazy vals are now encoded as a single ValDef
rather than a ValDef + DefDef pair. We need to treat ValDef-s
with the LAZY flag in the same way as we used to treat the
DefDef.
- Rename one of the symbols `ANF,anf` in the same scope to avoid
generating anonymous class names that differ only in case. The
compiler warned about this one.
- When patching the LabelDefs to have a `Unit` result type, propagate
this other LabelDefs conclude with a jump to that label. Not sure
why, but without this we now hit an error in the backend about the
nonsensical attempt to emit a coercion from void to int.
- Use crossScalaVersions in the build and update the Scala versions
tested in CI.
|
|\ \ \
| | | |
| | | | |
Rework extension point for checking for already-completed futures
|