Ollie Charles

You may wish to change the label of this repository then, which is currently "An efficient *PostgreSQL* driver and a flexible mapping API" (emphasis mine)

Ok, I thought that may be the case, but just wanted to check wrt the above comment.

`postgresql-simple` does this, which you might want to use for reference.

Personally I take the philosophy that most bugs lie at the boundaries of systems, and `hasql` is precisely there to interface between two systems. This is where a lot of...

I just found myself wanting `mapMaybe`. Even if there's no efficient way to implement it other than round-tripping through a list, it provides a nicer API for users, and is...

I'd like to suggest we bring back `forceWatch` for a different reason - using this with Storybook. Storybook seems to run its own server which means `compiler.watching` is `false`. I'm...

As an example of where the inference in `freer-simple` kills me, consider [`logging-effect`](https://hackage.haskell.org/package/logging-effect-1.3.2/docs/Control-Monad-Log.html) logging [`prettyprinter` `Doc`s](http://hackage.haskell.org/package/prettyprinter-1.2.1/docs/Data-Text-Prettyprint-Doc.html#g:1). I create my effect type: ```haskell data Log a where LogMsg :: a ->...

Glad you're open minded on this. To be honest, I can count on one hand the amount of times I've wanted multiple instances of one effect. I'd also note that...

I may explore ```haskell class MonadFoo a m | m -> a where sendFoo :: Foo a -> m a instance Member (Foo a) effs => MonadFoo a (Eff effs)...

`logMsg :: (IsString s, Member (Log s) effs) => s -> Eff effs ()` is not an unreasonable thing to consider writing, but is almost entirely unusable if you want...