Simon Chemouil

I don't think this approach works because of the identity conversion provided by `std`. ``` | impl From for MyNewType { | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | = note: conflicting implementation in crate...

Rust should be able to understand non-overlapping borrows. I need to test but I believe `&mut self.foo` should work because it does not overlap with `self.metrics`. If it doesn't, I...

> A question: Why does metered need to hold onto a &self.metrics? I'm not sure of the implementation details, but I'm assuming it's either storing that reference in a struct...

I think your solution was the original code and aliasing the metric a workaround at some point, but I don't remember the details. I would be open to test your...

So far the approach suggested uses `unsafe` but I think we should be able to find an alternative, maybe with a different layout, that does not and avoids risks of...

- [ ] https://blog.kraken.com/post/7964/oxidizing-kraken-improving-kraken-infrastructure-using-rust/ > We have been using async Rust first with Future combinators and using the async/await support as soon as it landed on nightly. It’s been an...

> At the same time, if I am going to make a crate to implement some protocol, or to develop byte-stream adapters for compression or what have you, I need...

I've also hit this issue. Since this is a heisenbug that anyone can get through cargo update, I suggest 0.3.18 be yanked and a 0.3.19 cut with a fix. I'd...

This would be a breaking change, but happy to consider a PR for this