David Tolnay

> I have put already \> 30 hours into just this RFC > I think I may need to create a bigger new RFC that would fix all of this...

@burdges regarding namespacing: Thanks! I know many people are excited about pursuing a namespacing scheme. I added a note that I think it should be pursued in a different RFC...

Thanks @withoutboats, that is an important drawback. Do any of the following characterize your perspective? 1. We can potentially make this proposal work as long as the responsibility for oversight...

@withoutboats ah that makes sense. At the same time don't forget the other half of the story which is bad feelings arising from our current policy. Some more questions to...

Thanks Sean -- this is waiting on me to update the RFC text for another round of discussion. Will get to it ASAP.

@pietroalbini this was written before a crates.io team existed and there wasn't *any* team whose jurisdiction this best fit. Which team(s) would you prefer to put in charge of the...

I am coming back to this RFC after a bit of time to sort out some other project ideas that had piled up waiting for my time (syn 1.0, [case...

I would prefer not to assert. The caller can wrap their iterator in an iterator adapter containing the assert if they want that. https://doc.rust-lang.org/std/primitive.slice.html#method.binary_search also does not verify that its...

#1876 discusses some ideas for how slicing could work for `CStr`.

See also: - https://github.com/rust-lang/rust/pull/26499, an unmerged implementation of `starts_with` and `ends_with` and discussion of generalizing the [`Pattern`](https://doc.rust-lang.org/std/str/pattern/trait.Pattern.html) API to `OsStr`. - https://github.com/rust-lang/rfcs/pull/1309, a promising RFC involving the `OsStr` API. -...