Workflow
safe-exceptions
Our great sponsors
Workflow | safe-exceptions | |
---|---|---|
1 | 3 | |
42 | 132 | |
- | 0.0% | |
0.0 | 3.4 | |
almost 8 years ago | 7 months 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.
Workflow
-
Event Sourcing
I was part of that debate, I remember a rather interesting point of discussion: Is the main operation "apply" or "dedup"
Apply seems to be the common notion of event sourcing: There is a function apply that takes a state an event and yields a new state. Then, starting in an init state and iteratively applying the entire event history, boom, latest state restored.
Dedup has a lot of charm though: Run and rerun your code, if that step of your code is executed for the first time (no corresponding event in the event history) execute the step and store its result as an event in the history, however, if that step of your code is executed for the second, third time (there is a corresponding event in the event history) do not execute the step and return its result from the event in the history. The Haskell Workflow Package (https://hackage.haskell.org/package/Workflow) is a good example
Temporal follows the second approach, so "proper" Event Sourcing? You be the judge :)
safe-exceptions
-
Spooky Masks and Async Exceptions
In case anyone is interested, there's a long discussion on this ticket. Still hoping somebody will respond to my comment.
-
Async Control Flow
In safe-exception and uniftio it was decided to rethrow the original exception exactly because they decided to use uninterruptibleMask, see here for details.
-
Why exactly I want Boring Haskell to happen
unliftio (and safe-exceptions) contains a very controversial choice of of using uninterruptibleMask inside its bracket. The argument for it seem to come from this issue and comes from the fact that one of the most popular resource finalizers hClose is interruptible. This is a simplification. It is interruptible only if a file handle is used concurrently. Such usage of file handles is rather odd, and it suggest wrong architecture, for example leaking file handles using concurrency. When using file handles in synchronous setting, what withFile pattern encourages, hClose will not block and thus mask is enough.
What are some alternatives?
cloud-haskell - This is an umbrella development repository for Cloud Haskell
ifcxt - constraint level if statements
unliftio - The MonadUnliftIO typeclass for unlifting monads to IO
unexceptionalio - IO without any PseudoExceptions
effect-monad - Provides 'graded monads' and 'parameterised monads' to Haskell, enabling fine-grained reasoning about effects.
atl - Arrow Transformer Library
record - Anonymous records
lens-tutorial - The missing tutorial module for the lens library
transient - A full stack, reactive architecture for general purpose programming. Algebraic and monadically composable primitives for concurrency, parallelism, event handling, transactions, multithreading, Web, and distributed computing with complete de-inversion of control (No callbacks, no blocking, pure state)
rio-orphans - A standard library for Haskell
time-warp