Open traviscross opened 1 month ago
The RFC largely documents how rustc and Miri already behave. So the main task here is to write suitable documentation -- not sure where the discussion of which NaNs can be generated would even go. Probably somewhere in the reference, but ideally mentioned in the f32
/f64
type docs as well, or so?
The other main outcome of this is that can we proceed with stabilization of https://github.com/rust-lang/rust/issues/57241.
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