Skip to content

CONTRIBUTING.md: Give some more examples of non-replacements #28

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
Turbo87 merged 1 commit into from
Jun 30, 2026
Merged

CONTRIBUTING.md: Give some more examples of non-replacements #28

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 CONTRIBUTING.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -31,9 +31,9 @@ Two kinds of entries qualify:
not all of it. The `description` must spell out what is still missing.

Coverage is judged by the dominant use case. If only a small slice of a crate's
purpose lives in `std`, it does not qualify. `itertools` is the canonical
exclusion: a handful of its adaptors have `std` equivalents, but the crate as a
whole is not replaced.
purpose lives in `std`, it does not qualify. Some canonical examples of
exclusions are `itertools`, `libc`, and `rustix`. Some of their functionality
has been added to `std`, but the crates are not replaced, in whole or in part.

## Maintainer notice-and-comment

Expand Down