throttled-io-loop
stm-containers
Our great sponsors
| throttled-io-loop | stm-containers | |
|---|---|---|
| - | 2 | |
| 1 | 62 | |
| - | - | |
| 0.0 | 3.7 | |
| almost 8 years ago | 5 days ago | |
| Haskell | Haskell | |
| BSD 3-clause "New" or "Revised" License | MIT License |
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
We haven't tracked posts mentioning throttled-io-loop yet.
Tracking mentions began in Dec 2020.
stm-containers
-
Software Transactional Memory (1997)
I think you are right about STM being roughly equivalent to snapshot isolation.
What STM offers is an easy way to invent "containers for snapshotted values" aka TVars. Using them carefully may result in better scaling: https://hackage.haskell.org/package/stm-containers
-
How to achieve "Run at most one parallel async action per user"?
how about use stm-containers?
What are some alternatives?
unagi-streams - Unagi-chan channels for io-streams.
stm-incremental - A very simple interface for incremental computation using STM in Haskell.
async - Run IO operations asynchronously and wait for their results
restricted-workers - Interactive-diagrams
flush-queue
stm-chunked-queues - Thread communication queues that group items/requests that occur close together in time
async-dejafu - Systematic concurrency testing meets Haskell.
theatre - Minimalistic actor library for Haskell
scheduler - A work stealing scheduler
named-lock - A named lock that is created on demand.
ki - A structured concurrency library
conceit - Concurrently + Either