Owen Shepherd

I wrote a RESP3 parser here: https://github.com/414owen/resp RESP3 adds quite a lot of new syntactic forms, but it's still possible to parse it without backtracking. It should be complete, but...

I have a branch of hedis that uses the RESP3 protocol [here](https://github.com/414owen/hedis/tree/os/resp3). It passes all the tests, apart from one of the protocol pipelining ones. I'm not yet convinced that...

Yeah the pub/sub listener needs to inspect messages constantly, to know if they're a push message. This means we don't get pipelining. One way around that is to have a...

I'm also seeing this behaviour

Sure, I have a library called `multi-except`, which lets you applicatively build up multiple errors. It exports them as a `NonEmpty`, and uses a non-empty dlist internally. I'm a big...

@nalchevanidze I've updated the stack.yaml with a lower and upper bound for attoparsec-aeson, but I'm afraid I'm a bit nodejs-phobic, would you be able to run that command for me?

I'm happy to take a stab at this. I've made changes that get the modules to show per-library. Seems to work fine. I'd also be in favour of listing dependencies...

Yep, that's all sensible. I'll optimise for lack of visual clutter. If I figure out how to display the dependencies per-library in an uncluttered way, it'll be in a separate...

I think you're definitely onto something, at least for the pathological case. A top-level split would also fix my qualm about dependencies not being per-library, as, if I'm picturing it...

@peterbecich Sure thing, I've removed the purple tinge from the text inputs :)