stm-queue-extras
stm-containers
Our great sponsors
| stm-queue-extras | stm-containers | |
|---|---|---|
| - | 2 | |
| 0 | 62 | |
| - | - | |
| 0.0 | 5.6 | |
| about 9 years ago | 6 months ago | |
| Haskell | Haskell | |
| Apache License 2.0 | 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.
stm-queue-extras
We haven't tracked posts mentioning stm-queue-extras 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?
named-lock - A named lock that is created on demand.
stm-incremental - A very simple interface for incremental computation using STM in Haskell.
stm-conduit - STM-based channels for conduits.
restricted-workers - Interactive-diagrams
stm-chunked-queues - Thread communication queues that group items/requests that occur close together in time
stm-hamt - STM-specialised Hash Array Mapped Trie
theatre - Minimalistic actor library for Haskell
conceit - Concurrently + Either