|9 days ago||5 days ago|
|Apache License 2.0||MIT 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.
The case against Effect Systems (e.g., the IO data type)
2 projects | reddit.com/r/scala | 18 Oct 2022
Hmm, you can write direct-style code with monad: https://github.com/rssh/dotty-cps-async allows this, exists support libraries exist for near all well-known effect systems: https://github.com/rssh/cps-async-connect, so you can use async/await with IO/ZIO the same as with Future. Although in IO style, any operation that mutates state is async, it's hard to write code where you should place `await` near each line. And it looks like automatic coloring is a too radical change of concepts for most functional programmers. The option to allow using <- in the direct style may be more popular, but this requires changes to the scala core. Another question - are we need effective systems to be present in each program in industrial-style development? Here I agree that mostly no.
New Scala 3 Codebases
6 projects | reddit.com/r/scala | 17 Feb 2022
Dotty-cps-async 0.9.7 is released.
4 projects | reddit.com/r/scala | 26 Jan 2022
This is a generic async/await transformer for scala3 which allows using effectful monads in the direct style. URL: (https://github.com/rssh/dotty-cps-async )
2 projects | reddit.com/r/ProgrammingLanguages | 14 Jul 2021
dotty-cps-async [rssh/dotty-cps-async ] with automatic coloring do something very similar in two steps. Automatic coloring defines implicit conversion F[A] => A as x => await(x)(m). The compiler inserts those awaits inside async blocks and then eliminates them later via cps-transform. Exists some limitations which we need to add for effect monads like IO (we don't want run effect twice and don't want to screw semantics of effects by extra memoizing). So, if your language has a possibility to implement effect monads, then you need a possibility to restrict using Flattenable.
Why does Scala seem to be slow at benchmark results?
6 projects | reddit.com/r/scala | 22 Oct 2022
You can use jsoniter-scala. It is easy to use like upickle.
Starting with scala
4 projects | reddit.com/r/scala | 7 Sep 2022
BEWARE: uJson is vulnerable under DoS attacks
Is Scala a good choice for a data intensive web backend?
5 projects | reddit.com/r/scala | 3 Sep 2022
Please see sources (and GitHub history of development) of jsoniter-scala as an example in the domain of JSON parsing and serialization.
Learning macros in scala 2.13
2 projects | reddit.com/r/scala | 4 Jun 2022
I suggest looking into jsoniter-scala Macro API it has unique support of both Scala 2 and Scala 3 in a source compatible manner.
Using SWAR techniques to speed up parsing and serialization from/to JSON
3 projects | reddit.com/r/scala | 30 Mar 2022
Since v2.13.6 release jsoniter-scala dropped support of Java 8: https://github.com/plokhotnyuk/jsoniter-scala/releases/tag/v2.13.63 projects | reddit.com/r/scala | 30 Mar 2022
SWAR (SIMD in register) techniques were used in the last release of jsoniter-scala to speed up parsing and serialization on JVM platforms.
Scala 3 compatible macro libraries
2 projects | reddit.com/r/scala | 1 Mar 2022
Try jsoniter-scala. It is a library with macros for handy deriving of safe and efficient JSON codecs that has Scala 3 support since v2.12.1
Every time I sit down to use an HTTP client and JSON parser, I get really frustrated
5 projects | reddit.com/r/scala | 20 Feb 2022
Use jsoniter-scala for handy auto-derive safe and efficient JSON codecs.
Scala3 adoption doubts
2 projects | reddit.com/r/scala | 17 Feb 2022
Here is a great example of macros migration from Scala 2 to Scala 3 that are source compatible and tested by the same test sources.2 projects | reddit.com/r/scala | 17 Feb 2022
Impressive work, although I'll stand by Scala 2 macros being a blocker -- I mean, look at this monster, nearly 3K lines of dense Scala 3 macro code to replicate functionality you already had in Scala 2. For most mortals that would be a gigantic endeavor, although a great learning experience I'm sure :)
What are some alternatives?
circe - Yet another JSON library for Scala
json4s - JSON library
DSL-JSON - High performance JVM JSON library
Play JSON - The Play JSON library
jackson-module-scala - Add-on module for Jackson (https://github.com/FasterXML/jackson) to support Scala-specific datatypes
spray-json - A lightweight, clean and simple JSON implementation in Scala
Jackson - Core part of Jackson that defines Streaming API as well as basic shared abstractions
None Is Not Null - JSON typeclasses that know the difference between null and absent fields
jawn - Jawn is for parsing jay-sawn (JSON)
scala-json - Compile-time JSON marshaling and abstraction for Scala, Scala Native and Scala.js
borer - Efficient CBOR and JSON (de)serialization in Scala
sbt-json - sbt plugin that generates Scala case classes for easy, statically typed and implicit access of JSON data e.g. from API responses