sbt-jni
SBT Plugin to ease working with JNI (by sbt)
dotty
The Scala 3 compiler, also known as Dotty. (by scala)
Our great sponsors
| sbt-jni | dotty | |
|---|---|---|
| 3 | 71 | |
| 123 | 5,669 | |
| 0.8% | 2.1% | |
| 7.6 | 10.0 | |
| 29 days ago | 4 days ago | |
| Scala | Scala | |
| BSD 3-clause "New" or "Revised" License | Apache License 2.0 |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
sbt-jni
Posts with mentions or reviews of sbt-jni.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2021-10-05.
-
Calling C code from Scala
I encourage you to go with sbt-jni, it also supports Rust/Cargo now ;)
-
Native code access from scala 3 without using Graal
Besides JNA, there's also sbt-jni or you can wait for Project Panama to deliver.
- sbt-jni 1.5.0 has been released: Notably support for Rust/Cargo and Scala 3. Using JNI from Scala has never been easier!
dotty
Posts with mentions or reviews of dotty.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-09-13.
-
RustRover – A Standalone Rust IDE by JetBrains
Dotty? Was it still the name later?
http://dotty.epfl.ch/
-
Does the fthomas/refined library work differently in Scala 3?
I think this might be related to this issue.
-
`boundary/break`: do you use it ? what do you do with it ?
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
-
Iron updates: turning opaque types into value objects
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
-
Reconnecting with Scala. What's new?
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
-
About Scala-Native
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.
-
I've started writing a book on Scala 3 Macros
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.
-
What is scala's modern Web API framework?
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).
-
scala 3 does not have :javap. Does anyone have any tips how to get around this.
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
-
Is the Scala Center really working on Scala 4?
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