restricted-workers
Interactive-diagrams (by co-dan)
async
Run IO operations asynchronously and wait for their results (by simonmar)
restricted-workers | async | |
---|---|---|
- | 3 | |
39 | 326 | |
- | 0.0% | |
0.0 | 2.8 | |
about 10 years ago | 19 days ago | |
Haskell | Haskell | |
BSD 3-clause "New" or "Revised" License | BSD 3-clause "New" or "Revised" License |
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.
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.
restricted-workers
Posts with mentions or reviews of restricted-workers.
We have used some of these posts to build our list of alternatives
and similar projects.
We haven't tracked posts mentioning restricted-workers yet.
Tracking mentions began in Dec 2020.
async
Posts with mentions or reviews of async.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-06-30.
-
Haskell FFI call safety and garbage collection
Here is a "bug" report that describes an example of such behavior: https://github.com/simonmar/async/issues/93
-
ki 1.0.0: a lightweight structured concurrency library
Are you referring to this? https://github.com/simonmar/async/issues/128
-
Rust async is colored, and that’s not a big deal
What do you mean by that? Blocking functions (without any yield points) certainly exist in Haskell, unless one uses -fno-omit-yields (see here).
What are some alternatives?
When comparing restricted-workers and async you can also consider the following projects:
streamly - High performance, concurrent functional programming abstractions
throttle-io-stream - Throttler between a producer and a consumer function
stm-containers - Containers for STM
unagi-chan - A haskell library implementing fast and scalable concurrent queues for x86, with a Chan-like API
theatre - Minimalistic actor library for Haskell