Mark f16 and f128 as incomplete features#127739
Mark f16 and f128 as incomplete features#127739tgross35 wants to merge 2 commits intorust-lang:masterfrom
f16 and f128 as incomplete features#127739Conversation
|
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