dotty-cps-async
scalaprops
Our great sponsors
dotty-cps-async | scalaprops | |
---|---|---|
10 | - | |
170 | 275 | |
- | -0.7% | |
9.4 | 8.3 | |
9 days ago | 7 days ago | |
Scala | Scala | |
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.
dotty-cps-async
-
Help a Kotlin convert back into Scala world
Now in scala we have direct mode transformers: dotty-cps-async [https://github.com/rssh/dotty-cps-async] with cps-async-connect [https://github.com/rssh/cps-async-connect ] supports all well-knowm monad stacks, for ZIO also exists ZIO-direct [https://github.com/zio/zio-direct ] , for IO - cats-effect-cps [https://github.com/typelevel/cats-effect-cps ], for kyo [https://github.com/fwbrasil/kyo ] - kyo-direct.
-
dotty-cps-async 0.9.12 is out
dotty-cps-async: https://github.com/rssh/dotty-cps-async
-
The case against Effect Systems (e.g., the IO data type)
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.
- dotty-cps-async 0.9.11 is out. (bugfixes and experimental loom support)
- dotty-cps-async 0.9.9
- New Scala 3 Codebases
- Also dotty-cps-async 0.9.8 with scala-native support
- dotty-cps-async 0.9.8 with scala-native support
-
Dotty-cps-async 0.9.7 is released.
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 )
-
Language-assisted Flattening
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.
scalaprops
We haven't tracked posts mentioning scalaprops yet.
Tracking mentions began in Dec 2020.
What are some alternatives?
scala3-example-project - An example sbt project that compiles using Dotty
ScalaTest - A testing tool for Scala and Java developers
cps-async-connect
ScalaCheck - Property-based testing for Scala
scala-3-migration-guide - The Scala 3 migration guide for everyone.
ScalaMeter - Microbenchmarking and performance regression testing framework for the JVM platform.
Rx.NET - The Reactive Extensions for .NET
µTest - A simple testing framework for Scala
scala-gopher - Implementation of CSP constructions (Communication Sequence Process, i.e. go-like channels) in scala
Specs2 - Software Specifications for Scala
libretto - Declarative concurrency and stream processing library for Scala
ScalaMock - Native Scala mocking framework