async
Run IO operations asynchronously and wait for their results (by simonmar)
stack-sizes
Tool to print stack usage information emitted by LLVM in human readable format (by japaric)
| async | stack-sizes | |
|---|---|---|
| 3 | 1 | |
| 316 | 51 | |
| - | - | |
| 4.2 | 0.0 | |
| about 2 months ago | over 1 year ago | |
| Haskell | Rust | |
| BSD 3-clause "New" or "Revised" License | Apache License 2.0 |
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.
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).
stack-sizes
Posts with mentions or reviews of stack-sizes.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2021-03-14.
-
Rust async is colored, and that’s not a big deal
In existing practice, there are some tools (including for Rust) to calculate maximum stack size in order to determine how large a stack should be allocated – but usually some manual work is required. Due to the inconvenience or perhaps mere unfamiliarity, most people don't use such tools; they just pick a number, perhaps do some rough testing, and hope for the best. That is both dangerous (especially on microcontrollers which often don't have memory protection and thus can't have a guard page to catch stack overflows), and wasteful (especially on microcontrollers which often have very small amounts of RAM). And it's actually somewhat more dangerous in Rust than in C, due to the ease of inadvertently allocating large temporaries on the stack, which may or may not be optimized away.
What are some alternatives?
When comparing async and stack-sizes you can also consider the following projects:
throttle-io-stream - Throttler between a producer and a consumer function
async-std - Async version of the Rust standard library
restricted-workers - Interactive-diagrams
async-combinators
streamly - High performance, concurrent functional programming abstractions
rwlock - A simple implementation of a multiple-reader / single-writer locks using STM
theatre - Minimalistic actor library for Haskell
consumers
kazura-queue
named-lock - A named lock that is created on demand.
conceit - Concurrently + Either
mvar-lock - A trivial lock based on MVar