Yep, it's worse than that. Code compiled for 2.x is _not allowed_ to work with 2.(x+1). I say this with all love for Scala and total respect for how big improvements in what Scala does necessarily mean bytecode-level incompatibility. But it'd be cooler to call these major releases! even in Java, you stand a chance of Java 6-era code still running on Java 14.
On Thu, Oct 31, 2019 at 4:14 PM Cody Koeninger <c...@koeninger.org> wrote: > > On Wed, Oct 30, 2019 at 5:57 PM Sean Owen <sro...@gmail.com> wrote: > > > Or, frankly, maybe Scala should reconsider the mutual incompatibility > > between minor releases. These are basically major releases, and > > indeed, it causes exactly this kind of headache. > > > > > Not saying binary incompatibility is fun, but 2.12 to 2.13 is a major > release, it's not a minor release. Scala pre-dates semantic > versioning, the second digit is for major releases. > > scala 2.13.0 Jun 7, 2019 > scala 2.12.0 Nov 2, 2016 > > --------------------------------------------------------------------- > To unsubscribe e-mail: dev-unsubscr...@spark.apache.org > --------------------------------------------------------------------- To unsubscribe e-mail: dev-unsubscr...@spark.apache.org
