cats-effect
cats-effect copied to clipboard
typelevel
The pure asynchronous runtime for Scala
## About this PR 📦 Updates [org.scala-sbt:sbt](https://github.com/sbt/sbt) from `1.10.2` to `1.10.3` 📜 [GitHub Release Notes](https://github.com/sbt/sbt/releases/tag/v1.10.3) - [Version Diff](https://github.com/sbt/sbt/compare/v1.10.2...v1.10.3) ## Usage ✅ **Please merge!** I'll automatically update this PR to resolve...
![typelevel-steward[bot] avatar](https://avatars.githubusercontent.com/u/3731824?v=4 "typelevel-steward[bot] avatar"){kind=avatar}
Adds an apply method for MapRef. If the Effect type is an instance of Async , the `ConcurrentHashMap` implementation will be used otherwise the `sharedImmutableMap` will be used with the...
Closes #4141. Benchmarks: ``` Throughput Async Concurrent enqueueDequeueMany 281.571 ± 4.388 ops/s 144.713 ± 2.057 ops/s enqueueDequeueOne 281.266 ± 4.599 ops/s 173.974 ± 3.129 ops/s GC alloc rate Async Concurrent...
I've been benchmarking otel4s [BatchSpanProcessor.scala](https://github.com/typelevel/otel4s/blob/main/sdk/trace/src/main/scala/org/typelevel/otel4s/sdk/trace/processor/BatchSpanProcessor.scala) and noticed a heavy memory consumption. One of the suspects is the dropping queue. Switching to `Queue.bounded` dropped memory usage by 30-40%. I added dropping...
This PR introduces a mechanism for checking if a given poller is "owned" by the current thread and thus is safe to interact with. This is useful primarily for cancelation,...
We currently have many `MapRef` implementations, based on `Ref[Map]`, sharding, `ConcurrentHashMap`, etc. We should have an `apply` constructor that chooses a reasonable default implementation, _probably_ `ConcurrentHashMap`.
https://typelevel.org/cats-effect/docs/core/io-local and https://typelevel.org/cats-effect/docs/std/supervisor (once the site redeploys) both include diagrams. Can we render these diagrams more nicely with mermaid?
Close #4093 by attempting self-cancel before `F.never`
This is my solution for #3757, As I discussed with @armanbilge, the new method requires `MonadCancelThrow` in order to use `Resource.allocatedCase` which handles releasing acquired resource(s) in case of error....
