safe-exceptions
haskelldb
Our great sponsors
safe-exceptions | haskelldb | |
---|---|---|
3 | 1 | |
132 | 99 | |
0.0% | - | |
3.4 | 0.0 | |
6 months ago | almost 5 years ago | |
Haskell | Haskell | |
MIT License | BSD 3-clause "New" or "Revised" 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.
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.
haskelldb
-
Why exactly I want Boring Haskell to happen
HaskellDB was principled but the codebase was somewhat bitrotted, it had dubious denotational semantics, it was possible to write crashing queries. and only worked with a special "record" form data types that it had cooked up. On the other hand once one accepted the special "records" everything else looked like familiar Haskell. Queries were written in do-notation.
What are some alternatives?
unexceptionalio - IO without any PseudoExceptions
HongoDB - A Simple Key Value Store
ifcxt - constraint level if statements
database-migrate - database-migrate haskell library to assist with migration for *-simple sql backends.
atl - Arrow Transformer Library
haskelldb-connect-hdbc-catchio-mtl - Bracketed HDBC session for HaskellDB
effect-monad - Provides 'graded monads' and 'parameterised monads' to Haskell, enabling fine-grained reasoning about effects.
mywatch
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)
perdure - Robust persistence for typed immutable data
time-warp
classy-influxdb-simple