Skip to content
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

Closed

Conversation

tgross35
Copy link
Contributor

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

@rustbot rustbot added S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. labels Jul 14, 2024
@tgross35
Copy link
Contributor Author

@rustbot author
@rustbot label +F-f16_and_F128

@rustbot rustbot added S-waiting-on-author Status: This is awaiting some action (such as code changes or more information) from the author. F-f16_and_f128 `#![feature(f16)]`, `#![feature(f128)]` and removed S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. labels Jul 14, 2024
@tgross35
Copy link
Contributor Author

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.

@rust-log-analyzer

This comment has been minimized.

@tgross35
Copy link
Contributor Author

@rustbot label +rla-silenced

@rustbot rustbot added the rla-silenced Silences rust-log-analyzer postings to the PR it's added on. label Jul 15, 2024
@scottmcm
Copy link
Member

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.

@scottmcm
Copy link
Member

Oh, bleh

  error: the feature `f128` is incomplete and may not be safe to use and/or cause compiler crashes
     --> library/std/src/lib.rs:295:12
      |
  295 | #![feature(f128)]
      |            ^^^^

Maybe that means this can't be marked incomplete, because we don't want to allow incomplete features in core :/

@tgross35
Copy link
Contributor Author

I just saw that, but it looks like this is enabled in core so maybe it's okay? It is a bit unfortunate that you can't enable a specific list of incomplete features, since the reason they are incomplete is quite a range.

@workingjubilee
Copy link
Member

Mmh.

@workingjubilee
Copy link
Member

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.

@tgross35
Copy link
Contributor Author

Good idea, opened #127741

@tgross35
Copy link
Contributor Author

Unfortunately clippy uses these features too so that's another allow(incomplete_features) :(

@tgross35 tgross35 closed this Jul 15, 2024
@tgross35 tgross35 deleted the f16-f128-incommplete-feature branch July 15, 2024 00:49
@tgross35
Copy link
Contributor Author

Ah, GH doesn't like me fixing a typo in my branch name. Reopened at #127743

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
F-f16_and_f128 `#![feature(f16)]`, `#![feature(f128)]` rla-silenced Silences rust-log-analyzer postings to the PR it's added on. S-waiting-on-author Status: This is awaiting some action (such as code changes or more information) from the author. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants