Skip to content

Rename libs-api to libs in docs #386

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
tmandry merged 1 commit into from
Aug 14, 2026
Merged

Rename libs-api to libs in docs #386

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions src/how_to/propose.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -124,11 +124,11 @@ In the diagram above, we show experiments as always leading to an RFC. This is t

### What about adding special traits and things to the standard library?

We consider intrinsics and "lang item" (things that need special treatment from the language) to be under the lang team purview. Specifically, the lang team governs the semantics and capabilities exposed by this new feature. The details of the API are governed by the [libs-api team].
We consider intrinsics and "lang item" (things that need special treatment from the language) to be under the lang team purview. Specifically, the lang team governs the semantics and capabilities exposed by this new feature. The details of the API are governed by the [libs team].

Whenever possible, though, we prefer to issue a quick approval for the "general feature" being discussed, and leave it to the libs-api team to decide where to apply it. For example, we approved the ability to add inherent methods to standard library types like `u32` long ago, but the [libs-api team] governs what APIs are available.
Whenever possible, though, we prefer to issue a quick approval for the "general feature" being discussed, and leave it to the libs team to decide where to apply it. For example, we approved the ability to add inherent methods to standard library types like `u32` long ago, but the [libs team] governs what APIs are available.

[libs-api team]: https://github.com/rust-lang/libs-team
[libs team]: https://github.com/rust-lang/libs-team

### My RFC has been waiting for a comment from the lang-team for a long time!

Expand Down