Falko Peters

First, I vehemently disagree that `Queued` is "confusing". It is what Redis commands return while in multi/exec mode. You even gave an example on Stackoverflow that illustrated the point of...

@qrilka, your scenario is impossible in Redis (and Hedis).

@benjamin-hodgson Don't be snide. Removing a Monad instance will not remove the need that people read the documentation of their database, or a compiler error will be the least of...

No worries. Unless @k-bx has a different view on this, I would postpone any changes to the multiExec API until 1. ApplicativeDo is widely available (at least in stack LTS,...

Regarding the three options: 1. Automatic pipelining is _the_ feature of Hedis. It's the coolest thing about it. In fact, coming up with the idea is the single reason why...

Your approach sounds good. A separate but compatible library is the way to go. `sendRequest` lets you send any command to Redis and you can wrap it some convenience functions,...

I like this feature, thanks for the pull request. But the code needs some more work. - I prefer `confColors :: Value -> [SGR]` to the `Value -> String` version,...

I like `Value -> [SRG]` because it offers a superset of the `JSONType -> [SRG]` functionality, while using existing types. You are right, that color-by-content is an unlikely case, but...

Hi Alexander, sorry for my late reply, I did not have time to look into your feature request. Can you describe the use case you have in mind a little...

@Nicowcow you are correct that _Hedis_ does not allow you to re-take control from pubSub unless a message arrives. This is arguably a bug, and at least a weakness of...