scala-3-migration-guide VS dotty-cps-async

Compare scala-3-migration-guide vs dotty-cps-async and see what are their differences.


The Scala 3 migration guide for everyone. (by scalacenter)
Our great sponsors
  • Zigi - The context switching struggle is real
  • InfluxDB - Build time-series-based applications quickly and at scale.
  • SonarQube - Static code analysis for 29 languages.
  • Scout APM - Truly a developer’s best friend
scala-3-migration-guide dotty-cps-async
2 8
238 122
-0.4% -
2.5 9.1
4 days ago 7 days ago
Scala Scala
Apache License 2.0 Apache License 2.0
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
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.


Posts with mentions or reviews of scala-3-migration-guide. We have used some of these posts to build our list of alternatives and similar projects.

We haven't tracked posts mentioning scala-3-migration-guide yet.
Tracking mentions began in Dec 2020.


Posts with mentions or reviews of dotty-cps-async. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2022-10-18.
  • The case against Effect Systems (e.g., the IO data type)
    2 projects | | 18 Oct 2022
    Hmm, you can write direct-style code with monad: allows this, exists support libraries exist for near all well-known effect systems:, 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 | | 17 Feb 2022
  • Dotty-cps-async 0.9.7 is released.
    4 projects | | 26 Jan 2022
    This is a generic async/await transformer for scala3 which allows using effectful monads in the direct style. URL: ( )
  • Language-assisted Flattening
    2 projects | | 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.

What are some alternatives?

When comparing scala-3-migration-guide and dotty-cps-async you can also consider the following projects:

Scalafix - Refactoring and linting tool for Scala

scala3-example-project - An example sbt project that compiles using Dotty

functional-way - Write small programs (eg -algorithms) in a functional way.

Rx.NET - The Reactive Extensions for .NET

scalaprops - property based testing library for Scala

jsoniter-scala - Scala macros for compile-time generation of safe and ultra-fast JSON codecs

scala-3-crash-course - Scala 3 workshop presenting the top new features of the language.

iron - Strong type constraints for Scala


libretto - Declarative concurrency and stream processing library for Scala

scala-gopher - Implementation of CSP constructions (Communication Sequence Process, i.e. go-like channels) in scala