Standard library implementation ownership #267
Description
Meeting proposal info
- Title: Standard library implementation ownership
- Type: non-technical
Summary
I am interested in whether it would make sense for the compiler team (or subteam / working group as appropriate) to own the standard library implementation, with libs owning only the library design going forward.
Brief pitch: It should be possible to do almost all the work of a libs team member without looking at the standard library in more detail than its rustdocs -- as much as the lang team can do their work independent of any specific implementation.
Brief motivation: This reflects an existing difference in on-ramp to design vs implementation work. If someone is sending PRs to revamp and optimize btree for example, are they going to be more interested in consensus-seeking about method names, or in implementation work across all of rust-lang/rust? At the same time, we are looking for ways to streamline the use of libs team bandwidth. The team selects for people with diverse library design experience, which means members tend to have active library projects outside the standard library; this is unlike the compiler team for whom their team role is usually their dominant project.
About this issue
This issue corresponds to a meeting proposal for the compiler team steering meeting. It corresponds to a possible topic of discussion. You can read more about the steering meeting procedure here.
Comment policy
These issues are meant to be used as an "announcements channel" regarding the proposal, and not as a place to discuss the technical details. Feel free to subscribe to updates. We'll post comments when reviewing the proposal in meetings or making a scheduling decision. In the meantime, if you have questions or ideas, ping the proposers on Zulip (or elsewhere).