--
You received this message because you are subscribed to the Google Groups "scala-internals" group.
To unsubscribe from this group and stop receiving emails from it, send an email to scala-interna...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Thanks for trying out the fix and for finding the next bug.
Yes, we do compile the library with -optimise. We also run all of the functional tests for the compiler with the optimizer during nightly builds and PR validation.
But in spite of this, being a non-default option, the optimizer gets far less real world testing than the rest of the compiler and isn’t of the quality that we’d like. We are in the process of replacing the optimizer in Scala 2.12 and have invested a bit more in unit testing and in integration testing (by enabling the optimizer in the builds of all the open source projects we track in our community build, so we hope to have a marked improvement in quality.
Regarding this bug, I’ve found the source of the regression and a workaround and noted these on the ticket.
It might be time to rename it -optimistic.