stm-containers
theatre
stm-containers | theatre | |
---|---|---|
2 | - | |
65 | 7 | |
- | - | |
5.2 | 4.1 | |
4 months ago | 11 months ago | |
Haskell | Haskell | |
MIT 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.
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?
theatre
We haven't tracked posts mentioning theatre yet.
Tracking mentions began in Dec 2020.
What are some alternatives?
stm-incremental - A very simple interface for incremental computation using STM in Haskell.
threads - Fork threads and wait for their result
restricted-workers - Interactive-diagrams
timeout - Generalized sleep and timeout functions
stm-chunked-queues - Thread communication queues that group items/requests that occur close together in time
ctrie - Non-blocking concurrent hashmap for Haskell
conceit - Concurrently + Either
lifted-async - Run lifted IO operations asynchronously and wait for their results
named-lock - A named lock that is created on demand.
simple-actors - A Haskell library providing an idiomatic implementation of the actor model of concurrency
ttrie - A contention-free STM hash map for Haskell
async - Run IO operations asynchronously and wait for their results