dotty-cps-async
libretto
Our great sponsors
dotty-cps-async | libretto | |
---|---|---|
10 | 2 | |
164 | 190 | |
- | - | |
9.4 | 9.4 | |
17 days ago | 11 days ago | |
Scala | Scala | |
Apache License 2.0 | Mozilla Public 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.
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.
- New Scala 3 Codebases
-
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.
libretto
-
Synit – A Reactive Operating System
I'm not sure this is actually easy to solve. The basic idea here seems to be that actors coordinate with the help of shared mutable state (the "dataspace"). At this point you're actually back to square one as synchronizing shared state is the core problem with distributed, concurrent systems…
Given that, and the fact that this whole thingy is untyped makes me skeptical. Not even the std. ingredients like type-state, session types, behavioral types, or the like seem to get used. I also don't see linear types here, which go very well with session types / behavioral types, and can help making typing message passing easier.
Also that this approach would be completely network transparent, as I see it, seems like a design flaw. One needs control over the various effects that can occur! Otherwise the points form "distributed systems future work" can't be solved, imho.
And form the practical point of view: There is no Akka / Pekko based Scala implementation? I'm quite surprised, to be honest.
Akka / Pekko is the actor runtime, and Scala is famous for it's eDSL features; besides of course its type-system, which makes thing like Libretto possible, which seems related here:
https://github.com/TomasMikula/libretto
Syndicate-lang looks OTOH more like the usual callback-hell.
But like I've said, I don't get this whole thingy really. I've just clicked through some parts of the web-sites. Most likely I'm just overlooking the elephant in the room. So would be glad to learn more!
(BTW: Very nice web-site design on all the projects. Especially nice typography. Really enjoyed this part while clicking through this stuff.)
- New Scala 3 Codebases
What are some alternatives?
scala3-example-project - An example sbt project that compiles using Dotty
cps-async-connect
scala-3-migration-guide - The Scala 3 migration guide for everyone.
Rx.NET - The Reactive Extensions for .NET
scala-gopher - Implementation of CSP constructions (Communication Sequence Process, i.e. go-like channels) in scala
dedav4s - Declarative Data Viz 4 Scala
jsoniter-scala - Scala macros for compile-time generation of safe and ultra-fast JSON codecs
woof - A pure Scala 3 logging library with no reflection
braid-spec - Working area for Braid extensions to HTTP
cats-effect-cps - An incubator project for async/await syntax support for Cats Effect