-
Notifications
You must be signed in to change notification settings - Fork 12.7k
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.
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
Mark f16
and f128
as incomplete features
#127739
Conversation
Is there any guideline for what constitutes an incomplete feature? The ABI issues and maybe missing symbols definitely seem to qualify this, but it seems that a missing trait impl/method relative to f32 & f64 (as per the original comment) wouldn't necessarily be in the same boat. |
This comment has been minimized.
This comment has been minimized.
@rustbot label +rla-silenced |
Thanks for making a PR! I don't know if there's a concrete definition. Personally, I tend to think of it as "we're not ready for experience reports because we know that if you try it you're going to hit stuff that doesn't work". Basically, a marker that you'll likely hit obvious problems and that we probably don't want bugs about those because we know it's not done yet. A "we need devs not users right now", kinda. |
Oh, bleh
Maybe that means this can't be marked |
(it is enabled in `core`)
I just saw that, but it looks like this is enabled in |
Mmh. |
Please open a bug for "incomplete features that std should not depend on" vs. "incomplete features that std... has to implement..." and cc Boxy and Nils about it. |
Good idea, opened #127741 |
Unfortunately clippy uses these features too so that's another |
Ah, GH doesn't like me fixing a typo in my branch name. Reopened at #127743 |
See #116909 (comment).
Unfortunately this will probably have a lot that needs to be updated, just getting this started to figure out exactly what that will be.
r? @scottmcm