Tracking Issue for float_semantics
RFC 3514
#128288
Labels
B-RFC-approved
Blocker: Approved by a merged RFC but not yet implemented.
C-tracking-issue
Category: A tracking issue for an RFC or an unstable feature.
F-float_semantics
`#![feature(float_semantics)]`
T-lang
Relevant to the language team, which will review and decide on the PR/issue.
This is a tracking issue for RFC 3514:
The feature gate for the issue is
#![feature(float_semantics)]
.About tracking issues
Tracking issues are used to record the overall progress of implementation. They are also used as hubs connecting to other relevant issues, e.g., bugs or open design questions. A tracking issue is however not meant for large scale discussion, questions, or bug reports about a feature. Instead, open a dedicated issue for the specific matter and add the relevant feature gate label.
Steps
Unresolved Questions
simd
intrinsics, and those are subject to the NaN-non-determinism described above. So the current de-facto semantics of at least some platform intrinsics is that they do not match what the platform does.Related
TODO.
cc @RalfJung @rust-lang/lang
The text was updated successfully, but these errors were encountered: