Dotty is coming
summary
Dotty becomes the reference implementation for Scala 3 and aims to ship over the next 2–3 years while coexisting with Scala 2; migration guidance includes avoiding fragile features (procedure syntax, some implicit-heavy tricks), using Scala Fix rewrites to convert code (e.g. procedure syntax, lazy val fixes), testing against the Dotty community build repo, and relying on the planned stable-ABI SIP to reduce binary churn. Practical changes: HLists/records in stdlib, Scala.meta macros supported (scala-reflect not), pattern-match performance rewrites, SBT/Zinc integration work, and tooling (linker/optimizer) to make migrated code faster.
AI-written summary · about
chapters (5)
- 0:00Start
- 2:29AGENDA • Building our common future - Feature status • Maintaining our common past • Binary compatibility stable Source compatibility, Scalafix - Dotty Community build
- 8:16A LOT OF NEW FEATURES ARE COMING Allowing • new ways to build library APIs • new approaches to structure library components • more efficient implementations of library internals
- 22:50DOTTY COMMUNITY BUILD Can be found in: Projects are build using Dotty nightlies • help us estimate complexity of migration • check Scalaix source conversion
- 49:25Scala Days Stay tuned
related talks
46mState of Scala
26mMigrating Gallia to Scala 3 the good, the bad and the very good
32mMaking Sotware Better, Despite Having Users
32mMaking software better despite having users
38mScalaJS and Typescript: an unlikely romance
49mThe Trouble With Types
48mTypelevel Scala: What does it mean ?
29mAging: Evolving Software, Tools, and Ourselves.
