|7 days ago||6 days ago|
|Apache License 2.0||Apache License 2.0|
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.
Which static analysis tool do you use for Scala?
8 projects | reddit.com/r/scala | 12 Jan 2022
There is also wartremover but you cannot run it separately from your compile command.
Newspeak and Domain Modeling
4 projects | news.ycombinator.com | 29 Jun 2021
or `NonUnitStatements` without explicit annotation.
This effectively locks you into writing pure code (you can extend the linter to cover other things like not using `Future` or not using Java libs outside of `MonadError` from cats). The linters operate on typed ASTs at compile time, and have plugins for the most popular scala build tools. Coupled with `-XFatalWarnings', you can guarantee that nothing unexpected happens unless you explicitly pop the escape hatch, for the most part.
You can still bring in external libraries that haven't been compiled with these safties in place, so you aren't completely safe, but if you use ZIO/Typelevel libraries you can be reasonably assured of referentially transparent code in practice.
There are three schools of thought, roughly, in the scala community towards the depth of using the type system and linters to provide guarantees and capabilities, currently:
1) Don't attempt to do this, it makes the barrier to entry to high for Scala juniors. I don't understand this argument - you want to allow runtime footguns you could easily prevent at compile time because the verifiable techniques take time to learn? Why did you even choose to use a typesafe language and pay the compilation time penalty that comes with it?
2) Abstract everything to the smallest possible dependency interface, including effects (code to an effect runtime, F[_] that implements the methods your code needs to run - if you handle errors, F implements MonadError, if you output do concurrent things, F implements Concurrent, etc.) and you extend the effect with your own services using tagless final or free.
3) You still use effect wrappers, but you bind the whole project always to use a concrete effect type, avoiding event abstraction, thus making it easier to code, and limiting footguns to a very particular subset (mainly threadpool providers and unsafeRun or equivalent being called eagerly in the internals of applications).
My opinion is that smallest interface with effect guarantees (#2) is best for very large, long maintenance window apps where thechoice of effect runtime might change(app), or is out of the devs' control (lib); and #3 is best for small apps.
TL/DR; You can go a really, really long way to guaranteeing effects don't run in user code in scala. Not all the way like Haskell, but far enough that it's painful to code without conforming to referential transparency.
Scala 3.2 released!
2 projects | reddit.com/r/scala | 8 Sep 2022
This was taken care of recently: https://github.com/lampepfl/dotty/pull/15540/files
Eval 0.1.0 released
A more limited way to do runtime evaluation is via the jsr-223 support: https://github.com/lampepfl/dotty/blob/main/tests/run-with-compiler/scripting.scala, you can't reflect on types that way but the advantage is that you don't end up depending on compiler-internals APIs that could change in any patch release.
https://github.com/lampepfl/dotty/issues/14262 points to https://github.com/invesdwin/invesdwin-context/blob/master/invesdwin-context-parent/invesdwin-context-scala/src/main/java/de/invesdwin/context/scala/pool/WrappedScalaScriptEngine.java which seems to be doing some caching via https://docs.oracle.com/javase/8/docs/api/javax/script/Compilable.html, but I have zero experience with this stuff.
Note though that our jsr-223 support is currently a bit limited compared to the scala 2 version: https://github.com/lampepfl/dotty/issues/14262
Issues setting up Scala 3 on Windows w/Coursier
3 projects | reddit.com/r/scala | 14 Mar 2022
If you could open an issue at https://github.com/lampepfl/dotty/issues detailing your problems with the bash shell on Windows that would be useful (it's likely our scripts have only been tested with the cmd.exe shell).
[Scaladoc, Scala3] Question about special character in URL in new Scaladoc in Scala3
2 projects | reddit.com/r/scala | 2 Mar 2022
That seems like a bug. Could you open an issue at https://github.com/lampepfl/dotty/issues?2 projects | reddit.com/r/scala | 2 Mar 2022
Scala 3 Reflection
5 projects | reddit.com/r/scala | 1 Feb 2022
- If you can't generate a quotation and need any strings, then the next option - add compiler to the classpath and use JSR223 scripting API: (example : https://github.com/lampepfl/dotty/blob/master/tests/run-with-compiler/scripting.scala
GraalVM native-image with Scala 3 reflection hell
3 projects | reddit.com/r/scala | 9 Jan 2022
See https://github.com/lampepfl/dotty/issues/13985, maybe the graalvm reflection config format could be enriched to support wildcards if it doesn't already?
‘Woof’, a pure Scala 3 logging library
2 projects | news.ycombinator.com | 18 Dec 2021
Who isn't waiting to finally get an usable effect system?
But there is something on the horizon for Scala:
One can have a proper effect system on the JVM also already today with Flix:
What are some alternatives?
Scapegoat - Scala compiler plugin for static code analysis
Scalastyle - scalastyle
sbt - sbt, the interactive build tool
Scalafix - Refactoring and linting tool for Scala
scalafmt - This repo is now a fork of --->
Linter - Static Analysis Compiler Plugin for Scala
scalajs-benchmark - Benchmarks: write in Scala or JS, run in your browser. Live demo:
Scalatex - Programmable, Typesafe Document Generation
Mill - Your shiny new Java/Scala build tool!
Slick - Slick (Scala Language Integrated Connection Kit) is a modern database query and access library for Scala
Scurses - Scurses, terminal drawing API for Scala, and Onions, a Scurses framework for easy terminal UI