Friedel Ziegelmayer
Friedel Ziegelmayer
> That way we can add `.unwrap()` things. The reason I don't want to use `unwrap` is that for me that is a sign of "Error" that should never happen...
> Or add a custom `unwrap_or_abort` method where we want to abort? That's a lot more explicit. If we can find a shorter name I would be okay with an...
I guess we are sticking with `?` then :P
maybe simply putting all Future related things behind a feature flag, such that as a user this can be set at compile time
So my goal with how it is currently stored was to have internally the same byte representation as go-multiaddr has. If we move away from that, there needs to be...
I think this would be great in terms of reducing the overhead in the various scenarios.
I like the idea. I am not sure though if the "special reset message with random bytes" could be problematic or not. An alternative which ties into this would be...
Right, I guess that works then. Might still be useful to expand to have it available as close message in other states of the protocol
@yyoncho I did :( and emacs kept hanging and ignored my keyboard input
This is my lsp config: https://gist.github.com/dignifiedquire/d6f06aaf197ad790f899d9a6092657d9