See sbt/sbt#4125 for context.
Open a shell and
git checkout "x=1"
Now run sbt
on a different shell and do ~test
. Once it runs for the first time,
git checkout "x=2"
Take a look at the test passing, and the definitions of x
and y
.
Incremental compilation when used together with the optimizer generates incorrect bytecode: modifications in methods/vals are not propagated to wherever they are being inlined.
The incremental compiler should not ever generate incorrect bytecode.
sbt 1.1.0
most likely previous ones too.