-
-
Notifications
You must be signed in to change notification settings - Fork 15k
Incomplete features in std: required for implementation vs. should not use #127741
Copy link
Copy link
Open
Labels
A-lintsArea: Lints (warnings about flaws in source code) such as unused_mut.Area: Lints (warnings about flaws in source code) such as unused_mut.T-compilerRelevant to the compiler team, which will review and decide on the PR/issue.Relevant to the compiler team, which will review and decide on the PR/issue.T-libsRelevant to the library team, which will review and decide on the PR/issue.Relevant to the library team, which will review and decide on the PR/issue.
Description
Metadata
Metadata
Assignees
Labels
A-lintsArea: Lints (warnings about flaws in source code) such as unused_mut.Area: Lints (warnings about flaws in source code) such as unused_mut.T-compilerRelevant to the compiler team, which will review and decide on the PR/issue.Relevant to the compiler team, which will review and decide on the PR/issue.T-libsRelevant to the library team, which will review and decide on the PR/issue.Relevant to the library team, which will review and decide on the PR/issue.
Type
Fields
Give feedbackNo fields configured for issues without a type.
We currently allow
incomplete_featuresinstdbut notcore. It came up in #127739 (markingf16andf128as incomplete) that there is a difference between incomplete features thatstdneeds to be able to work with or that are incomplete because of what is instd(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.