Jarred Allen

I've observed this on rust nightly (both `rustc 1.61.0-nightly (532d3cda9 2022-02-23)` and `rustc 1.61.0-nightly (10cc7a6d0 2022-02-26)` (the latest nightly release), as well as some older versions that I no longer...

I'm admittedly not much of a UI person (so feel free to suggest a different position if you want), but I was just thinking of putting it at the top...

> Aren't these the same as the `first_chunk`/`split_first_chunk` and similar methods? These are similar, but my proposed methods modify `self` in place (hence the `&mut &'a Self` signature).

> I don't think it makes sense to provide methods that require `&mut [T]` but return `&[T]`. It is pretty easy to split and reassign the slice in a single...

+1 on the eventual `FromIntegerLiteral` const trait that lets you make arbitrary types from integer literals via parsing a token string, but (as an outsider who isn't in the loop...

Can we also put this information into `rustdoc` output? That would have saved me some headache in the past from crates that poorly document whether a function blocks or returns...

For me personally, I'd prefer if mutexes were listed as blocking. If a mutex guards a short enough critical section, so then (using the lint reasons feature that's about to...