throttled-io-loop
By AxialExchange
async
Run IO operations asynchronously and wait for their results (by simonmar)
Our great sponsors
throttled-io-loop | async | |
---|---|---|
- | 3 | |
1 | 315 | |
- | - | |
0.0 | 3.9 | |
almost 8 years ago | about 1 month 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.
throttled-io-loop
Posts with mentions or reviews of throttled-io-loop.
We have used some of these posts to build our list of alternatives
and similar projects.
We haven't tracked posts mentioning throttled-io-loop 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 throttled-io-loop and async you can also consider the following projects:
unagi-streams - Unagi-chan channels for io-streams.
throttle-io-stream - Throttler between a producer and a consumer function
flush-queue
restricted-workers - Interactive-diagrams
async-dejafu - Systematic concurrency testing meets Haskell.
async-combinators
scheduler - A work stealing scheduler
streamly - High performance, concurrent functional programming abstractions
ki - A structured concurrency library
rwlock - A simple implementation of a multiple-reader / single-writer locks using STM
stm-conduit - STM-based channels for conduits.
theatre - Minimalistic actor library for Haskell
throttled-io-loop vs unagi-streams
async vs throttle-io-stream
throttled-io-loop vs flush-queue
async vs restricted-workers
throttled-io-loop vs async-dejafu
async vs async-combinators
throttled-io-loop vs scheduler
async vs streamly
throttled-io-loop vs ki
async vs rwlock
throttled-io-loop vs stm-conduit
async vs theatre