Jeff Burdges

You cannot beat the curried languages for expressiveness: If you consider the original example `round(sqrt(abs(sum(x))), 2)` then you would write this in Haskell as ``(`round` 2) . sqrt . abs...

We selected quinn because we do distributed systems and quinn aims more towards being a general purpose crate, while the other two aim more towards their specific use cases, like...

You'll run into trouble with `!Send` and `!Sync` there. Also, curl looks limited for custom TLS handling. And unsure if it handles the server side. I've no idea about your...

It's a nice example of serde's shortcomings. Afaik, crypto crates typically either avoid serde entirely, thus serde to serde users only care about one or two formats, or else define...

I donno if the parser can manage `?` but it should probably only be used for error handling. `it` might likely break too much existing code. Could we get away...

You missed some @Diggsey like ``` foo(|x,y| bar(|a| a+y) + x) foo(|x| bar(|_,b| x+b) + x) ``` I'm worried this might create a barrier to polymorphic closures.

It'd be cool if unsized_return could return into some future unsized_local, which sounds impossible with the alloca crate. An unsized_local that's less natural feeling sounds reasonable though. Anyways, the alloca...

Is there still some "commitment" to the original RFC motivation of passing unsized values? Ala ``` fn takes_closure(f: dyn FnOnce()) { f(); } ``` It feels like more explicit schemes...

RFC9390 requires an XoF, and gives sha2 xmd as a named cipher suite, but RFC9390 permits choosing another XoF like shake128 instead. I guess maybe the traits expose this option?

Alright, so already possible to choose shake128 with this PR? nice :)