Our great sponsors
-
-
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
You want Kernmantle, which quite honestly shouldn't be hard to implement around Cats and cats-effect. In particular, although Kernmantle doesn't require the use of the Arrow typeclass, there happen to be Arrow (actually ArrowChoice) instances for both Function1 from the standard library and Kleisli from Cats itself, given a Monad instance for the Kleilsi's F[_] type parameter. In other words, we should be able to port Kernmantle from Haskell to Scala (with the Typelevel ecosystem) and instantly be able to use pretty much anything else from the Typelevel ecosystem, or wrapped with it, in our workflow graphs. Pure functions, monadic functions, applicative functions, GADTs with hand-written interpreters, any of it. I think this would be eminently worth doing.
You want Kernmantle, which quite honestly shouldn't be hard to implement around Cats and cats-effect. In particular, although Kernmantle doesn't require the use of the Arrow typeclass, there happen to be Arrow (actually ArrowChoice) instances for both Function1 from the standard library and Kleisli from Cats itself, given a Monad instance for the Kleilsi's F[_] type parameter. In other words, we should be able to port Kernmantle from Haskell to Scala (with the Typelevel ecosystem) and instantly be able to use pretty much anything else from the Typelevel ecosystem, or wrapped with it, in our workflow graphs. Pure functions, monadic functions, applicative functions, GADTs with hand-written interpreters, any of it. I think this would be eminently worth doing.
If I understand correctly, it should be easier if you can use Scala 3. I played around with GADTs in Scala 3, they're much more ergonomic than Scala 2 https://github.com/massimosiani/type-driven-development-scala