sbt-tpolecat
sbt-jni
Our great sponsors
sbt-tpolecat | sbt-jni | |
---|---|---|
6 | 3 | |
371 | 123 | |
1.3% | 0.8% | |
7.3 | 7.6 | |
9 days ago | 29 days ago | |
Scala | Scala | |
Apache License 2.0 | BSD 3-clause "New" or "Revised" License |
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-tpolecat
-
Scala Resurrection
I'm awed by the maturity of the Scala 2 compiler. Every minor version in the 2.13 series adds a new linting improvement. You can see that if you have sbt-tpolecat in your project. I'm always happy to see that some option from Wartremover is no longer used.
-
Why are effects better for retries than Future?
Note that this assumes that non-Unit values are silently thrown away, which you should always configure scalac, preferably via sbt-tpolecat, not to allow.
-
New to Scala;
sbt-tpolecat to automatically provide reasonable Scala compiler settings.
-
Scala and Java Upgrade strategy
Start with settings strict compiler flags if you haven't already, for instance using sbt-tpolecat. This will help you remove the most obvious warts in your codebase.
-
Which static analysis tool do you use for Scala?
However, after a while, I found that most of the things I needed were already covered by the compiler. And that Rob's (aka tpolecat) list of compiler options provided all the ones I needed for my style of coding. I Then learn that there was this sbt plugin that managed the list for me and also took care of changing the options according to the Scala version.
-
Is there a way to beautify the code after Scala 3 migration?
Sorry, have nothing useful to contribute (although I'd recommend you to set a restrictive set of scalac flags, for example from sbt-tpolecat, to let compiler help you), but just wanted to praise the Scala team and remind us of all those "Python 3 situation" rants we've saw 2 years ago and how silly they look now.
sbt-jni
-
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!
What are some alternatives?
scaluzzi - Additional rules for Scalafix. The part of scalazzi rules.
sbt-native-packager - sbt Native Packager
Scalafix - Refactoring and linting tool for Scala
bazel-multiversion - Bazel rules to resolve, fetch and manage 3rdparty JVM dependencies with support for multiple parallel versions of the same dependency. Powered by Coursier.
scalafix-organize-imports - A CI-friendly Scalafix semantic rule for organizing imports
JavaCV - Java interface to OpenCV, FFmpeg, and more
sbt-dependency-check - SBT Plugin for OWASP DependencyCheck. Monitor your dependencies and report if there are any publicly known vulnerabilities (e.g. CVEs). :rainbow:
ox - Safe direct style concurrency and resiliency for Scala on the JVM
Wartremover - Flexible Scala code linting tool
sbt-release - A release plugin for sbt
skunk - A data access library for Scala + Postgres.
dotty - The Scala 3 compiler, also known as Dotty.