| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
the old code would fail with e.g.
> ++2.12.5-bin-76f588e-SNAPSHOT
> testOnly *WarningsSpec
this was showing up repeatedly when running the Scala community
build against as-yet-unmerged scala/scala PRs
|
| | |
|
| |
|
|
|
| |
we need to handle a Scala version like `2.13.0-pre-5e84129`,
as we see in nightly builds before bincompat is locked down
|
| |
|
|
| |
And remove unused code.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
If we blindly splicing `{..$stats, ..$generatedCode}`, and the last
expression in `$stats` is of type `Nothing`, we'll incur a dead
code warning when typechecking the block.
This commit:
- introduces a helper method to augment user-written stats with
synthetic code
- Emit a try/finally in that code (so we advance the state, even if we
are about to exit the state machine in the async-block global
exception handler
- Hide `Nothing` typed expressions from the dead code analysis
by wrapping them in an `expr: Any`
Fixes #150 (the part reported in the comments, not the original ticket.)
|
| | |
|
| | |
|
| |
|
|
| |
2013 must have been unlucky.
|
| |
|
|
|
|
| |
We were relying on an internal API that no longer exists.
We also need to tweak the way our tests infer scalaBinaryVersion.
|
| |
|
|
| |
This allows us to cross build against 2.10.x and 2.11.x.
|
| | |
|
| | |
|
| |
|
|
| |
Why suffer SI-4695 needlessly?
|
| |
|
