segfault

Results 61 comments of segfault

I think this is a sufficient implementation for what I am talking about (if you agree it is desirable). Although someone may have suggestions. Someone could argue that Uri should...

``` bash$ uname -r 5.10.10-arch1-1 ```

Based on the documentation, it seems you are meant to be able to set the priority of tiebreakers by specifying multiple. From what I can tell, with `--tac` you cannot...

I hit this problem on a weekly basis.

would you rather have unlimited bacon, but no docs or no bacon... but no docs

![image](https://user-images.githubusercontent.com/6549542/177691829-6e935b12-e315-43e1-af95-63bfd523cceb.png) Get rekt trolls

Similarly, it may make sense for Senders and Receivers to have traits to gain access to their opposite type. Though I think there are some issue with that idea

playing around ```rust // Maybe this should hold the sender and receiver pub struct Mpsc(std::marker::PhantomData); pub trait Channel { type Sender: postage::sink::Sink; type Receiver: postage::stream::Stream; fn new() -> (Self::Sender, Self::Receiver);...

I wrote this 2 years ago in 1 commit. I'm amazed anyone is even looking at it :)

Does anybody know what the major obsticle is? Neither this nor baritone support elytra, despite the obvious benefit. I am assuming there is a reason.