jumpnbrownweasel

> I think the **_ =** syntax is much better than the other alternatives such as _unused_ or _discard_. If things don't matter towards understanding what code does, they should...

> Any compiler checks for detecting use after assigning to `unused` should just as easily be applicable to `_`. Sorry, I wasn't clear and it is possible I'm wrong. I...

In case it helps to have another way of saying it, I think I understand the direction Sean's describing: recovered val arrays would be optimized whenever possible to store them...

I think it's very important that a library using anyhow can choose to disable backtraces without setting an env variable. Libraries should never set env variables for several reasons including...

The scenario I was referring to was where a library needs to avoid creation of backtraces in errors, and this should not be under the control of the app. The...

I can't find a way to suppress this short of adding `#[allow(unused_braces)]` for the entire module. Adding it above the struct doesn't work. There are also unused warnings generated. ```...

When `read_at` and `write_at` are added, please be sure to use a `&self` param rather than `&mut self`. Among other benefits, this would allow me to create a cache of...

Hello! I was looking at @ahrens comment in the earlier #73 issue [here](https://github.com/tokio-rs/tokio-uring/pull/73#issuecomment-1191836475) about being able to provide custom direct buffers by implementing traits. This made me wonder whether it...

@csnover Thank you very much for doing this work! I [posted](https://users.rust-lang.org/t/modular-bitfield-crate-has-recent-updates/129249) on URLO to let others know.