Michael Walker

I prefer keeping the dot with the type variables, because unlike `=>` and `->` it's not conceptually a type-level operator. This would make the multi-line version `:: forall t m.`...

This is something I've been interested in for a while (added to my to-do list in October 2018!) but I've just never got around to trying it out. Is there...

Another thought: what about keeping `MonadConc`, and keeping dejafu written in terms of it, and having a `concurrency-backpack` package which defines the signature, and implementations in terms of `IO` and...

`safe-exceptions` uses the typeclasses from the [`exceptions`](http://hackage.haskell.org/package/exceptions) library, which dejafu also uses, so I think all the `safe-exceptions` functionality will just work, except for: - `throwTo` - because it uses...

> For `unliftio`, could one bridge the constraints from `concurrency` with that from `unliftio`? You could certainly make a type which is an instance of both `concurrency` and `unliftio` (well,...

Thanks for opening an issue, it looks like you've found a bug. > `trace exhausted without reading a to-do point!` This means that dejafu has got into a loop somehow,...

I've managed to track it down to a smaller example: ```haskell import Test.DejaFu import Test.DejaFu.Conc.Internal.STM import Control.Concurrent.Classy hiding (wait) import Control.Concurrent.Classy.Async testInboundConnectionLimit :: Program (WithSetup (ModelTVar IO Int)) IO Int...

The obvious solution to this made matters worse, somehow. **Before** ``` 89,073,483,552 bytes allocated in the heap 20,134,704,256 bytes copied during GC 13,426,968 bytes maximum residency (6623 sample(s)) 265,720 bytes...

I had a quick go at this, [linked](https://github.com/barrucadu/dejafu/files/1546117/vector.diff.txt) is an almost working patch against bd64dfe. There's one test failure: ``` Independent Read Independent Write: :SQ: [Failed] Failed: Expected: Right ((0,1),(0,0))...

We now show what tags are available, I think that's probably enough.