cats-effect
cats-effect copied to clipboard
typelevel
The pure asynchronous runtime for Scala
Best practice is for `mapK` methods to require constraints on the target effect, not the original effect.
`cats.mtl.Local`'s semantics are a safe and useful subset of what can be done with `IOLocal`. This provides easy access to a `Local[F, E]` instance from an `IOLocal[E]` value. * core...
Using CE 3.5.4, invoking a `Dispatcher#unsafeRunSync` in a program run with `TestControl` appears to deadlock ```scala //> using dep "org.typelevel::cats-effect-testkit:3.5.4" import cats.effect.IOApp import cats.effect.IO import cats.effect.std.Dispatcher import scala.concurrent.duration._ import cats.effect.testkit.TestControl...
tutorial referenced: https://typelevel.org/cats-effect/docs/core/scala-native ```scala //> using dep "org.typelevel::cats-effect:3.5.4" import cats.effect.{IO, IOApp} object Main extends IOApp.Simple { def run: IO[Unit] = IO.println("Hello Cats Effect!") } ``` ``` $ time scala-cli --power...
The first step towards cross-platform `IORuntimeMetrics`. This PR also introduces a cross-platform `CpuStarvationMetrics`. ### Motivation It would be nice to have an option to access runtime metrics without relying on...
The PR is influenced by #3135. In my opinion, `Retry` must carry the error type. That way, we can implement retry functionality on top of the `Handle` from the `cats-mtl`....
As mentioned in https://github.com/typelevel/cats-effect/pull/3890#issuecomment-2227063576, this is the PR taking over #3890 to add a specialized version of `memoized` for `Resource`. Ref #3513
GraalVM is no longer available under the free license: https://github.com/graalvm/setup-graalvm#notes-on-oracle-graalvm-for-jdk-17 sbt-typelevel already did the same: https://github.com/typelevel/sbt-typelevel/pull/763
### Motivation `MapRef` can be considered as a replacement for `Ref[F, Map[K, V]]`. However, currently, there is no way to retrieve all available values. #### Why not add `snapshot` method...