Ben Plommer
Ben Plommer
The build is failing on use-site exhaustivity checks - what change would be required to fix them, and is it possible to change `WithContext` so that a use-site change isn't...
Much cleaner! Is the plan still to do this for 1.0? I'm happy to lend a hand if so.
> How about I reserve the merge conflicts and get this approved to ensure we're not the only two who like it, and then I can hand it off to...
On the topic of difficult-to-parse type signatures, one thing that might help is to use more meaningful names for type parameters - for example the constructor for `Autoslash` could change...
> What is `Rt`? "Routes"? Yep, wanted something more meaningful than `F` but still sufficiently cryptic to not get mistaken for a concrete type. Specific naming is subject to bikeshedding...
What's the next step on this, just pull the chances out into individual PRs that can be merged one by one?
> I guess I'm confused if we why if we really need both `F{_]` and `G{_]`. If one is `IO` and the other is `Kleisli`, can't we just use `Kleisli`...
> more functional A lot of http is defined in terms of side-effecting algorithms, which at least in some cases take precedence over the ABNF grammars in case of disagreement....
> > A lot of http is defined in terms of side-effecting algorithms, > > Do you have an example? Things like HPACK in HTTP/2 updating a table? All the...
How does this relate to `HttpCodec`? That seems to have been added and a few instances provided but then forgotten.