Incomplete features in `std`: required for implementation vs. should not use
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 119k
- Forks
- 16.1k
- PR merge metrics
- PR metrics pending
Description
We currently allow incomplete_features in std but not core. It came up in https://github.com/rust-lang/rust/pull/127739 (marking f16 and f128 as incomplete) that there is a difference between incomplete features that std needs to be able to work with or that are incomplete because of what is in std (such as the new types), and those that just should not be used.
Being able to allow specific incomplete features seems like it would be nice, if possible.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading this issue and the referenced pull request #127739, focusing on the distinction between incomplete features required by std and features that should not be used. Done would mean a decided and implemented way to allow only the appropriate incomplete features in std, with the corresponding core behavior addressed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- compilers
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100