Skip to content

remove forever-deprecated and hidden f64 methods#153975

Open
cyrgani wants to merge 1 commit intorust-lang:mainfrom
cyrgani:remove-f64-methods
Open

remove forever-deprecated and hidden f64 methods#153975
cyrgani wants to merge 1 commit intorust-lang:mainfrom
cyrgani:remove-f64-methods

Conversation

@cyrgani
Copy link
Copy Markdown
Contributor

@cyrgani cyrgani commented Mar 16, 2026

The methods f64::is_positive and f64::is_negative were deprecated since 1.0 and marked as #[doc(hidden)] in favor of f64::is_sign_positive and f64::is_sign_negative. They also only exist on f64, not on f32. But for some unknown reason, they have been marked as stable.

This PR proposes to remove both methods as they were never a part of the documented API, assuming that a crater run finds no significant breakage.

@cyrgani cyrgani added I-libs-api-nominated Nominated for discussion during a libs-api team meeting. needs-crater This change needs a crater run to check for possible breakage in the ecosystem. labels Mar 16, 2026
@rustbot rustbot added S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. T-libs Relevant to the library team, which will review and decide on the PR/issue. labels Mar 16, 2026
@rustbot
Copy link
Copy Markdown
Collaborator

rustbot commented Mar 16, 2026

r? @joboet

rustbot has assigned @joboet.
They will have a look at your PR within the next two weeks and either review your PR or reassign to another reviewer.

Use r? to explicitly pick a reviewer

Why was this reviewer chosen?

The reviewer was selected based on:

  • Owners of files modified in this PR: @scottmcm, libs
  • @scottmcm, libs expanded to 8 candidates
  • Random selection from Mark-Simulacrum, joboet, scottmcm

@jieyouxu
Copy link
Copy Markdown
Member

@bors try @craterbot check

@rust-bors

This comment has been minimized.

rust-bors bot pushed a commit that referenced this pull request Mar 17, 2026
remove forever-deprecated and hidden `f64` methods
@rust-bors
Copy link
Copy Markdown
Contributor

rust-bors bot commented Mar 17, 2026

☀️ Try build successful (CI)
Build commit: 63132bd (63132bd615c9bf75e93af8405d00064212331708, parent: 3645249d79dfb136b5d8de3ce153d19d6698d92d)

@jieyouxu
Copy link
Copy Markdown
Member

@craterbot check

@craterbot
Copy link
Copy Markdown
Collaborator

👌 Experiment pr-153975 created and queued.
🤖 Automatically detected try build 63132bd
🔍 You can check out the queue and this experiment's details.

ℹ️ Crater is a tool to run experiments across parts of the Rust ecosystem. Learn more

@craterbot craterbot added S-waiting-on-crater Status: Waiting on a crater run to be completed. and removed S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. labels Mar 17, 2026
@Amanieu
Copy link
Copy Markdown
Member

Amanieu commented Mar 17, 2026

Assuming crater results come back clean...

@rfcbot merge libs-api

@Amanieu Amanieu removed the I-libs-api-nominated Nominated for discussion during a libs-api team meeting. label Mar 17, 2026
@rust-rfcbot
Copy link
Copy Markdown
Collaborator

rust-rfcbot commented Mar 17, 2026

Team member @Amanieu has proposed to merge this. The next step is review by the rest of the tagged team members:

No concerns currently listed.

Once a majority of reviewers approve (and at most 2 approvals are outstanding), this will enter its final comment period. If you spot a major issue that hasn't been raised at any point in this process, please speak up!

See this document for info about what commands tagged team members can give me.

@rust-rfcbot rust-rfcbot added proposed-final-comment-period Proposed to merge/close by relevant subteam, see T-<team> label. Will enter FCP once signed off. disposition-merge This issue / PR is in PFCP or FCP with a disposition to merge it. labels Mar 17, 2026
@scottmcm
Copy link
Copy Markdown
Member

r=me assuming FCP completes and crater is clean 🙂

r? scottmcm

@rustbot rustbot assigned scottmcm and unassigned joboet Mar 18, 2026
@craterbot
Copy link
Copy Markdown
Collaborator

🚧 Experiment pr-153975 is now running

ℹ️ Crater is a tool to run experiments across parts of the Rust ecosystem. Learn more

@craterbot
Copy link
Copy Markdown
Collaborator

🎉 Experiment pr-153975 is completed!
📊 5 regressed and 5 fixed (854500 total)
📊 6128 spurious results on the retry-regressed-list.txt, consider a retry1 if this is a significant amount.
📰 Open the summary report.

⚠️ If you notice any spurious failure please add them to the denylist!
ℹ️ Crater is a tool to run experiments across parts of the Rust ecosystem. Learn more

Footnotes

  1. re-run the experiment with crates=https://crater-reports.s3.amazonaws.com/pr-153975/retry-regressed-list.txt

@craterbot craterbot added S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. and removed S-waiting-on-crater Status: Waiting on a crater run to be completed. labels Mar 22, 2026
@cyrgani cyrgani removed the needs-crater This change needs a crater run to check for possible breakage in the ecosystem. label Mar 22, 2026
@scottmcm scottmcm added S-waiting-on-fcp Status: PR is in FCP and is awaiting for FCP to complete. and removed S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. labels Mar 29, 2026
@WaffleLapkin
Copy link
Copy Markdown
Member

Looked at the crater report, it is indeed clean :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

disposition-merge This issue / PR is in PFCP or FCP with a disposition to merge it. proposed-final-comment-period Proposed to merge/close by relevant subteam, see T-<team> label. Will enter FCP once signed off. S-waiting-on-fcp Status: PR is in FCP and is awaiting for FCP to complete. T-libs Relevant to the library team, which will review and decide on the PR/issue.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

9 participants