Skip to content

Commit ac910ce

Browse files
RalfJungslanterns
andauthored
fix typo
Co-authored-by: Slanterns <slanterns.w@gmail.com>
1 parent b9ff02a commit ac910ce

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

text/0000-float-semantics.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -26,7 +26,7 @@ It's time to stop leaving our users in the dark about what actually is and is no
2626
[guide-level-explanation]: #guide-level-explanation
2727

2828
Primitive operations on floating-point types generally produce results that exactly match IEEE 754-2008:
29-
if you never use `to_bits`, `from_bits`, `is_sign_negative`, or `is_sign_poitive`, nor any unsafe operations that are equivalent to these safe methods, then your code will behave perfectly deterministically according to the IEEE specification.
29+
if you never use `to_bits`, `from_bits`, `is_sign_negative`, or `is_sign_positive`, nor any unsafe operations that are equivalent to these safe methods, then your code will behave perfectly deterministically according to the IEEE specification.
3030
In fact, this is true even if you do use these operations as long as you never call them on a NaN (or, in case of `from_bits`, use them to produce a NaN).
3131

3232
If you *do* use these operations on NaNs, then the exact behavior you see can depend on compiler version, compiler flags, target architecture, and it can even be non-deterministic (i.e., running the same operation on the same inputs twice can yield different results).

0 commit comments

Comments
 (0)