IEEE 754 is not an RFC #87419
IEEE 754 is not an RFC #87419
Conversation
|
(rust-highfive has picked a reviewer for you, use r? to override) |
rust-highfive
added
the
S-waiting-on-review
|
Random drive-by comment: to me, the version with |
|
I've always seen it written IEEE 754 or IEEE 754-2019 (or whatever date your favorite version was released on). |
|
@bors r+ rollup=always |
|
📌 Commit 30b6197 has been approved by |
bors
added
S-waiting-on-bors
In my experience you cite with the edition when you want to pin on that specific document and not intend to follow later editions when they come into effect in the future. So I think keeping just Note that one can always visit the normative pages for most standards and consider using there preferred citation. In this case:
|
IEEE 754 is not an RFC If there were something between `IEEE` and `754`, it would be `STD`: [`IEEE STD 754-2019`](https://doi.org/10.1109%2FIEEESTD.2019.8766229)
…arth Rollup of 9 pull requests Successful merges: - rust-lang#87348 (Fix span when suggesting to add an associated type bound) - rust-lang#87359 (Remove detection of rustup and cargo in 'missing extern crate' diagnostics) - rust-lang#87370 (Add support for powerpc-unknown-freebsd) - rust-lang#87389 (Rename `known_attrs` to `expanded_inert_attrs` and move to rustc_expand) - rust-lang#87395 (Clear up std::env::set_var panic section.) - rust-lang#87403 (Implement `AssignToDroppingUnionField` in THIR unsafeck) - rust-lang#87410 (Mark `format_args_nl` as `#[doc(hidden)]`) - rust-lang#87419 (IEEE 754 is not an RFC) - rust-lang#87422 (DOC: remove unnecessary feature crate attribute from example code) Failed merges: r? `@ghost` `@rustbot` modify labels: rollup
If there were something between
IEEEand754, it would beSTD:IEEE STD 754-2019