llogiq
llogiq
I guess you could reference [matklad's post on the topic](https://matklad.github.io/2022/03/26/self-modifying-code.html) unless you really want to write your own take.
A different solution (albeit possibly equaly volatile) would be to use rust-analyzer's backend. It works on stable Rust, is packaged in crates and has type & trait information. If needed,...
I think it's not exactly trivial, but the two steps are 1. Detect if we return unit (get the type, check if unit) 2. Get the Span `.lo`, go backwards...
Also to implement @camsteffen 's suggestion, adding a plain `Index::index` call to a known-panicky type such as slice.
Weird. For some reason it couldn't compile the fixed code!?
Thank you! @bors r+
Shouldn't that be ``` /// Retrieves a copy of the `i`-th element of `slice`. /// # Panics /// Panics if `i` is outside bounds. /// /// # Examples /// ```should_panic...
Yes. Our docs should follow the recommended style.
Manish seems to be pretty busy lately. So I've just had a look and I think it makes sense to sort; makes it easier to find things. Thank you for...
This could still be a pedantic lint, I feel it fits perfectly in that category.