Skip to content

Tracking issue for #![feature(const_float_classify)] #72505

@ecstatic-morse

Description

@ecstatic-morse
Contributor

Tracking issue for the #![feature(const_float_classify)] feature gate, which makes the following methods on f32 and f64 const fn:

  • classify
  • is_nan
  • is_infinite
  • is_finite
  • is_subnormal
  • is_normal
  • is_sign_positive
  • is_sign_negative

These require #72447 (#![feature(const_float_bits_conv)]), so this is transitively blocked on #57241.

Activity

added
C-tracking-issueCategory: An issue tracking the progress of sth. like the implementation of an RFC
T-libs-apiRelevant to the library API team, which will review and decide on the PR/issue.
on May 23, 2020
added a commit that references this issue on Jun 12, 2020
802a9ac
added
A-floating-pointArea: Floating point numbers and arithmetic
B-unstableBlocker: Implemented in the nightly compiler and unstable.
Libs-TrackedLibs issues that are tracked on the team's project board.
on Jul 29, 2020
added a commit that references this issue on Aug 23, 2020
RalfJung

RalfJung commented on Aug 3, 2024

@RalfJung
Member

#57241 is being proposed for stabilization, so this feature is also finally (transitively) unblocked. :)

Note that #114486 should also be reverted when is_nan becomes const-stable.

3 remaining items

added
disposition-mergeThis issue / PR is in PFCP or FCP with a disposition to merge it.
on Sep 12, 2024
added
final-comment-periodIn the final comment period and will be merged soon unless new substantive objections are raised.
and removed
proposed-final-comment-periodProposed to merge/close by relevant subteam, see T-<team> label. Will enter FCP once signed off.
on Sep 24, 2024
rfcbot

rfcbot commented on Sep 24, 2024

@rfcbot

🔔 This is now entering its final comment period, as per the review above. 🔔

added
to-announceAnnounce this issue on triage meeting
and removed
final-comment-periodIn the final comment period and will be merged soon unless new substantive objections are raised.
on Oct 4, 2024
rfcbot

rfcbot commented on Oct 4, 2024

@rfcbot

The final comment period, with a disposition to merge, as per the review above, is now complete.

As the automated representative of the governance process, I would like to thank the author for their work and everyone else who contributed.

This will be merged soon.

added a commit that references this issue on Oct 4, 2024
added
A-const-evalArea: Constant evaluation, covers all const contexts (static, const fn, ...)
on Dec 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

A-const-evalArea: Constant evaluation, covers all const contexts (static, const fn, ...)A-floating-pointArea: Floating point numbers and arithmeticB-unstableBlocker: Implemented in the nightly compiler and unstable.C-tracking-issueCategory: An issue tracking the progress of sth. like the implementation of an RFCLibs-TrackedLibs issues that are tracked on the team's project board.T-libs-apiRelevant to the library API team, which will review and decide on the PR/issue.disposition-mergeThis issue / PR is in PFCP or FCP with a disposition to merge it.finished-final-comment-periodThe final comment period is finished for this PR / Issue.

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

    Development

    Participants

    @RalfJung@dtolnay@apiraino@KodrAus@rfcbot

    Issue actions

      Tracking issue for `#![feature(const_float_classify)]` · Issue #72505 · rust-lang/rust