Scala Native VS dotty

Links: - https://dotty.epfl.ch/ - https://scala-native.org/en/stable/ - https://www.scala-js.org/ - https://typelevel.org/ - https://zio.dev/ - https://github.com/scala-native/scala-native/pull/3120 - https://github.com/lampepfl/dotty/pull/16517 - https://dotty.epfl.ch/docs/reference/experimental/index.html - https://scala-cli.virtuslab.org/ - https://scalameta.org/metals/ - https://docs.scala-lang.org/scala3/guides/migration/compatibility-intro.html - https://www.scala-lang.org/blog/2023/04/18/faster-scalajs-development-with-frontend-tooling.html - https://www.scala-lang.org/blog/2022/08/17/long-term-compatibility-plans.html

There's a plant of topics in which we might need help. To name a few, we might need some help in [porting the remaining JSR-166 types](https://github.com/scala-native/scala-native/issues/3165) to Scala Native shipped with future experimental multithreading support, but also large parts of the Java standard library need some improvements or reimplementations. Last but not least, we need people dedicated to the optimization of our current toolchain to make it use fewer resources and allow for faster builds.

Scala Native could have been this language, but at this stage I don't see it happening.

good stuff there is https://scala-native.org/ and http://www.scala-js.org/ then, I suppose?

Please vote for dropping Scala 2.11 support in Scala.js (https://github.com/scala-js/scala-js/issues/4759) and Scala Native (https://github.com/scala-native/scala-native/issues/2780)

I presume only the JVM version of Scala can use Loom but scala-native (https://scala-native.org/) and scala-js (https://www.scala-js.org/) can't use Loom. Similarly with Kotlin, the JVM Kotlin gets Loom, but the native and Javascript backends do not.

Nope. Scala Native is (still) single threaded, just like you are in e.g. Python or Node.js.

Until recently, there was only 64-bit support. 32-bit support is coming, though, see this pr. This means that you will be able to target 32-bit microcontrollers soon. Anything lower than 32-bit might not be realistic.

The release is binary compatible with previous ones, but Scala 3 on its own does not fully source compatible - more info about that in https://github.com/scala-native/scala-native/pull/2480 The full release is planned for the first weeks of January.

Dotty? Was it still the name later?

http://dotty.epfl.ch/

I think this might be related to this issue.

You can look (and EPFL collect feedback) about EPFL implementation of async/await: https://github.com/lampepfl/async. Also you can look at dotty ticket about this: https://github.com/lampepfl/dotty/pull/16739

The reason I’m not currently an opaque type user as they do not play well with the tagless final style we use, though I am patiently awaiting some attention on my bug report: https://github.com/lampepfl/dotty/issues/17281

Links: - https://dotty.epfl.ch/ - https://scala-native.org/en/stable/ - https://www.scala-js.org/ - https://typelevel.org/ - https://zio.dev/ - https://github.com/scala-native/scala-native/pull/3120 - https://github.com/lampepfl/dotty/pull/16517 - https://dotty.epfl.ch/docs/reference/experimental/index.html - https://scala-cli.virtuslab.org/ - https://scalameta.org/metals/ - https://docs.scala-lang.org/scala3/guides/migration/compatibility-intro.html - https://www.scala-lang.org/blog/2023/04/18/faster-scalajs-development-with-frontend-tooling.html - https://www.scala-lang.org/blog/2022/08/17/long-term-compatibility-plans.html

Scala Native has much more control on how the Scala AST is compiled, and can easier workaround platform limitations, eg. lazy vals in Scala 3 required reflection config for Native Image (see this and that), while in Scala Native we could mitigate problems with unsupported usage inside in other ways within the compiler plugin.

By the way, you might be interested in this recent PR which overhauls the scala 3 macro docs: https://github.com/lampepfl/dotty/pull/17060.

For example, this issue (https://github.com/lampepfl/dotty/issues/12840) was blocking the migration, it was reported more than a year ago and the fix was finally released a month ago (https://github.com/lampepfl/dotty/releases/tag/3.3.0-RC2).

For the record, there is an implementation of :javap which is close to being done but might need a volunteer to get it over the finish line: https://github.com/lampepfl/dotty/pull/12210

im glad to tell you that in 3.3.0 a lot of these -Wunused lints will be supported: see https://github.com/lampepfl/dotty/pull/16157