Primitive Typef32
Expand description
A 32-bit floating-point type (specifically, the “binary32” type defined in IEEE 754-2008).
This type can represent a wide range of decimal numbers, like3.5,27,-113.75,0.0078125,34359738368,0,-1. So unlike integer types(such asi32), floating-point types can represent non-integer numbers,too.
However, being able to represent this wide range of numbers comes at thecost of precision: floats can only represent some of the real numbers andcalculation with floats round to a nearby representable number. For example,5.0 and1.0 can be exactly represented asf32, but1.0 / 5.0 resultsin0.20000000298023223876953125 since0.2 cannot be exactly representedasf32. Note, however, that printing floats withprintln and friends willoften discard insignificant digits:println!("{}", 1.0f32 / 5.0f32) willprint0.2.
Additionally,f32 can represent some special values:
- −0.0: IEEE 754 floating-point numbers have a bit that indicates their sign, so −0.0 is apossible value. For comparison −0.0 = +0.0, but floating-point operations can carrythe sign bit through arithmetic operations. This means −0.0 × +0.0 produces −0.0 anda negative number rounded to a value smaller than a float can represent also produces −0.0.
- ∞ and−∞: these result from calculationslike
1.0 / 0.0. - NaN (not a number): this value results fromcalculations like
(-1.0).sqrt(). NaN has some potentially unexpectedbehavior:- It is not equal to any float, including itself! This is the reason
f32doesn’t implement theEqtrait. - It is also neither smaller nor greater than any float, making itimpossible to sort by the default comparison operation, which is thereason
f32doesn’t implement theOrdtrait. - It is also consideredinfectious as almost all calculations where oneof the operands is NaN will also result in NaN. The explanations on thispage only explicitly document behavior on NaN operands if this defaultis deviated from.
- Lastly, there are multiple bit patterns that are considered NaN.Rust does not currently guarantee that the bit patterns of NaN arepreserved over arithmetic operations, and they are not guaranteed to beportable or even fully deterministic! This means that there may be somesurprising results upon inspecting the bit patterns,as the same calculations might produce NaNs with different bit patterns.This also affects the sign of the NaN: checking
is_sign_positiveoris_sign_negativeona NaN is the most common way to run into these surprising results.(Checkingx >= 0.0orx <= 0.0avoids those surprises, but also how negative/positivezero are treated.)See the section below for what exactly is guaranteed about the bit pattern of a NaN.
- It is not equal to any float, including itself! This is the reason
When a primitive operation (addition, subtraction, multiplication, ordivision) is performed on this type, the result is rounded according to theroundTiesToEven direction defined in IEEE 754-2008. That means:
- The result is the representable value closest to the true value, if thereis a unique closest representable value.
- If the true value is exactly half-way between two representable values,the result is the one with an even least-significant binary digit.
- If the true value’s magnitude is ≥
f32::MAX+ 2(f32::MAX_EXP−f32::MANTISSA_DIGITS− 1), the result is ∞ or −∞ (preserving thetrue value’s sign). - If the result of a sum exactly equals zero, the outcome is +0.0 unlessboth arguments were negative, then it is -0.0. Subtraction
a - bisregarded as a suma + (-b).
For more information on floating-point numbers, seeWikipedia.
See also thestd::f32::consts module.
§NaN bit patterns
This section defines the possible NaN bit patterns returned by floating-point operations.
The bit pattern of a floating-point NaN value is defined by:
- a sign bit.
- a quiet/signaling bit. Rust assumes that the quiet/signaling bit being set to
1indicates aquiet NaN (QNaN), and a value of0indicates a signaling NaN (SNaN). In the following wewill hence just call it the “quiet bit”. - a payload, which makes up the rest of the significand (i.e., the mantissa) except for thequiet bit.
The rules for NaN values differ betweenarithmetic andnon-arithmetic (or “bitwise”)operations. The non-arithmetic operations are unary-,abs,copysign,signum,{to,from}_bits,{to,from}_{be,le,ne}_bytes andis_sign_{positive,negative}. Theseoperations are guaranteed to exactly preserve the bit pattern of their input except for possiblychanging the sign bit.
The following rules apply when a NaN value is returned from an arithmetic operation:
The result has a non-deterministic sign.
The quiet bit and payload are non-deterministically chosen fromthe following set of options:
- Preferred NaN: The quiet bit is set and the payload is all-zero.
- Quieting NaN propagation: The quiet bit is set and the payload is copied from any inputoperand that is a NaN. If the inputs and outputs do not have the same payload size (i.e., for
ascasts), then- If the output is smaller than the input, low-order bits of the payload get dropped.
- If the output is larger than the input, the payload gets filled up with 0s in the low-orderbits.
- Unchanged NaN propagation: The quiet bit and payload are copied from any input operandthat is a NaN. If the inputs and outputs do not have the same size (i.e., for
ascasts), thesame rules as for “quieting NaN propagation” apply, with one caveat: if the output is smallerthan the input, dropping the low-order bits may result in a payload of 0; a payload of 0 is notpossible with a signaling NaN (the all-0 significand encodes an infinity) so unchanged NaNpropagation cannot occur with some inputs. - Target-specific NaN: The quiet bit is set and the payload is picked from a target-specificset of “extra” possible NaN payloads. The set can depend on the input operand values.See the table below for the concrete NaNs this set contains on various targets.
In particular, if all input NaNs are quiet (or if there are no input NaNs), then the output NaNis definitely quiet. Signaling NaN outputs can only occur if they are provided as an inputvalue. Similarly, if all input NaNs are preferred (or if there are no input NaNs) and the targetdoes not have any “extra” NaN payloads, then the output NaN is guaranteed to be preferred.
The non-deterministic choice happens when the operation is executed; i.e., the result of aNaN-producing floating-point operation is a stable bit pattern (looking at these bits multipletimes will yield consistent results), but running the same operation twice with the same inputscan produce different results.
These guarantees are neither stronger nor weaker than those of IEEE 754: IEEE 754 guaranteesthat an operation never returns a signaling NaN, whereas it is possible for operations likeSNAN * 1.0 to return a signaling NaN in Rust. Conversely, IEEE 754 makes no statement at allabout which quiet NaN is returned, whereas Rust restricts the set of possible results to theones listed above.
Unless noted otherwise, the same rules also apply to NaNs returned by other library functions(e.g.min,minimum,max,maximum); other aspects of their semantics and which IEEE 754operation they correspond to are documented with the respective functions.
When an arithmetic floating-point operation is executed inconst context, the same rulesapply: no guarantee is made about which of the NaN bit patterns described above will bereturned. The result does not have to match what happens when executing the same code atruntime, and the result can vary depending on factors such as compiler version and flags.
§Target-specific “extra” NaN values
target_arch | Extra payloads possible on this platform |
|---|---|
aarch64,arm,arm64ec,loongarch64,powerpc (except whentarget_abi = "spe"),powerpc64,riscv32,riscv64,s390x,x86,x86_64 | None |
nvptx64 | All payloads |
sparc,sparc64 | The all-one payload |
wasm32,wasm64 | If all input NaNs are quiet with all-zero payload: None. Otherwise: all payloads. |
For targets not in this table, all payloads are possible.
§Algebraic operators
Algebraic operators of the forma.algebraic_*(b) allow the compiler to optimizefloating point operations using all the usual algebraic properties of real numbers –despite the fact that those properties donot hold on floating point numbers.This can give a great performance boost since it may unlock vectorization.
The exact set of optimizations is unspecified but typically allows combining operations,rearranging series of operations based on mathematical properties, converting between divisionand reciprocal multiplication, and disregarding the sign of zero. This means that the results ofelementary operations may have undefined precision, and “non-mathematical” valuessuch as NaN, +/-Inf, or -0.0 may behave in unexpected ways, but these operationswill never cause undefined behavior.
Because of the unpredictable nature of compiler optimizations, the same inputs may producedifferent results even within a single program run.Unsafe code must not rely on any propertyof the return value for soundness. However, implementations will generally do their best topick a reasonable tradeoff between performance and accuracy of the result.
For example:
May be rewritten as:
Implementations§
Source§implf32
implf32
1.0.0 (const: 1.90.0) ·Sourcepub const fnfloor(self) ->f32
pub const fnfloor(self) ->f32
Returns the largest integer less than or equal toself.
This function always returns the precise result.
§Examples
1.0.0 (const: 1.90.0) ·Sourcepub const fnceil(self) ->f32
pub const fnceil(self) ->f32
Returns the smallest integer greater than or equal toself.
This function always returns the precise result.
§Examples
1.0.0 (const: 1.90.0) ·Sourcepub const fnround(self) ->f32
pub const fnround(self) ->f32
Returns the nearest integer toself. If a value is half-way between twointegers, round away from0.0.
This function always returns the precise result.
§Examples
1.77.0 (const: 1.90.0) ·Sourcepub const fnround_ties_even(self) ->f32
pub const fnround_ties_even(self) ->f32
Returns the nearest integer to a number. Rounds half-way cases to the numberwith an even least significant digit.
This function always returns the precise result.
§Examples
1.0.0 (const: 1.90.0) ·Sourcepub const fntrunc(self) ->f32
pub const fntrunc(self) ->f32
Returns the integer part ofself.This means that non-integer numbers are always truncated towards zero.
This function always returns the precise result.
§Examples
1.0.0 (const: 1.90.0) ·Sourcepub const fnfract(self) ->f32
pub const fnfract(self) ->f32
1.0.0 ·Sourcepub fnmul_add(self, a:f32, b:f32) ->f32
pub fnmul_add(self, a:f32, b:f32) ->f32
Fused multiply-add. Computes(self * a) + b with only one roundingerror, yielding a more accurate result than an unfused multiply-add.
Usingmul_addmay be more performant than an unfused multiply-add ifthe target architecture has a dedicatedfma CPU instruction. However,this is not always true, and will be heavily dependant on designingalgorithms with specific target hardware in mind.
§Precision
The result of this operation is guaranteed to be the roundedinfinite-precision result. It is specified by IEEE 754 asfusedMultiplyAdd and guaranteed not to change.
§Examples
letm =10.0_f32;letx =4.0_f32;letb =60.0_f32;assert_eq!(m.mul_add(x, b),100.0);assert_eq!(m * x + b,100.0);letone_plus_eps =1.0_f32+ f32::EPSILON;letone_minus_eps =1.0_f32- f32::EPSILON;letminus_one = -1.0_f32;// The exact result (1 + eps) * (1 - eps) = 1 - eps * eps.assert_eq!(one_plus_eps.mul_add(one_minus_eps, minus_one), -f32::EPSILON * f32::EPSILON);// Different rounding with the non-fused multiply and add.assert_eq!(one_plus_eps * one_minus_eps + minus_one,0.0);1.38.0 ·Sourcepub fndiv_euclid(self, rhs:f32) ->f32
pub fndiv_euclid(self, rhs:f32) ->f32
Calculates Euclidean division, the matching method forrem_euclid.
This computes the integern such thatself = n * rhs + self.rem_euclid(rhs).In other words, the result isself / rhs rounded to the integernsuch thatself >= n * rhs.
§Precision
The result of this operation is guaranteed to be the roundedinfinite-precision result.
§Examples
1.38.0 ·Sourcepub fnrem_euclid(self, rhs:f32) ->f32
pub fnrem_euclid(self, rhs:f32) ->f32
Calculates the least nonnegative remainder ofself (mod rhs).
In particular, the return valuer satisfies0.0 <= r < rhs.abs() inmost cases. However, due to a floating point round-off error it canresult inr == rhs.abs(), violating the mathematical definition, ifself is much smaller thanrhs.abs() in magnitude andself < 0.0.This result is not an element of the function’s codomain, but it is theclosest floating point number in the real numbers and thus fulfills thepropertyself == self.div_euclid(rhs) * rhs + self.rem_euclid(rhs)approximately.
§Precision
The result of this operation is guaranteed to be the roundedinfinite-precision result.
§Examples
1.0.0 ·Sourcepub fnpowi(self, n:i32) ->f32
pub fnpowi(self, n:i32) ->f32
Raises a number to an integer power.
Using this function is generally faster than usingpowf.It might have a different sequence of rounding operations thanpowf,so the results are not guaranteed to agree.
§Unspecified precision
The precision of this function is non-deterministic. This means it varies by platform, Rust version, andcan even differ within the same execution from one invocation to the next.
§Examples
1.0.0 ·Sourcepub fnpowf(self, n:f32) ->f32
pub fnpowf(self, n:f32) ->f32
1.0.0 ·Sourcepub fnsqrt(self) ->f32
pub fnsqrt(self) ->f32
1.0.0 ·Sourcepub fnexp(self) ->f32
pub fnexp(self) ->f32
1.0.0 ·Sourcepub fnexp2(self) ->f32
pub fnexp2(self) ->f32
1.0.0 ·Sourcepub fnln(self) ->f32
pub fnln(self) ->f32
Returns the natural logarithm of the number.
This returns NaN when the number is negative, and negative infinity when number is zero.
§Unspecified precision
The precision of this function is non-deterministic. This means it varies by platform, Rust version, andcan even differ within the same execution from one invocation to the next.
§Examples
letone =1.0f32;// e^1lete = one.exp();// ln(e) - 1 == 0letabs_difference = (e.ln() -1.0).abs();assert!(abs_difference <=1e-6);Non-positive values:
1.0.0 ·Sourcepub fnlog(self, base:f32) ->f32
pub fnlog(self, base:f32) ->f32
Returns the logarithm of the number with respect to an arbitrary base.
This returns NaN when the number is negative, and negative infinity when number is zero.
The result might not be correctly rounded owing to implementation details;self.log2() can produce more accurate results for base 2, andself.log10() can produce more accurate results for base 10.
§Unspecified precision
The precision of this function is non-deterministic. This means it varies by platform, Rust version, andcan even differ within the same execution from one invocation to the next.
§Examples
letfive =5.0f32;// log5(5) - 1 == 0letabs_difference = (five.log(5.0) -1.0).abs();assert!(abs_difference <=1e-6);Non-positive values:
1.0.0 ·Sourcepub fnlog2(self) ->f32
pub fnlog2(self) ->f32
Returns the base 2 logarithm of the number.
This returns NaN when the number is negative, and negative infinity when number is zero.
§Unspecified precision
The precision of this function is non-deterministic. This means it varies by platform, Rust version, andcan even differ within the same execution from one invocation to the next.
§Examples
lettwo =2.0f32;// log2(2) - 1 == 0letabs_difference = (two.log2() -1.0).abs();assert!(abs_difference <=1e-6);Non-positive values:
1.0.0 ·Sourcepub fnlog10(self) ->f32
pub fnlog10(self) ->f32
Returns the base 10 logarithm of the number.
This returns NaN when the number is negative, and negative infinity when number is zero.
§Unspecified precision
The precision of this function is non-deterministic. This means it varies by platform, Rust version, andcan even differ within the same execution from one invocation to the next.
§Examples
letten =10.0f32;// log10(10) - 1 == 0letabs_difference = (ten.log10() -1.0).abs();assert!(abs_difference <=1e-6);Non-positive values:
1.0.0 ·Sourcepub fnabs_sub(self, other:f32) ->f32
👎Deprecated since 1.10.0: you probably meant(self - other).abs(): this operation is(self - other).max(0.0) except thatabs_sub also propagates NaNs (also known asfdimf in C). If you truly need the positive difference, consider using that expression or the C functionfdimf, depending on how you wish to handle NaN (please consider filing an issue describing your use-case too).
pub fnabs_sub(self, other:f32) ->f32
(self - other).abs(): this operation is(self - other).max(0.0) except thatabs_sub also propagates NaNs (also known asfdimf in C). If you truly need the positive difference, consider using that expression or the C functionfdimf, depending on how you wish to handle NaN (please consider filing an issue describing your use-case too).The positive difference of two numbers.
- If
self <= other:0.0 - Else:
self - other
§Unspecified precision
The precision of this function is non-deterministic. This means it varies by platform, Rust version, andcan even differ within the same execution from one invocation to the next.This function currently corresponds to thefdimf from libc on Unixand Windows. Note that this might change in the future.
§Examples
1.0.0 ·Sourcepub fncbrt(self) ->f32
pub fncbrt(self) ->f32
Returns the cube root of a number.
§Unspecified precision
The precision of this function is non-deterministic. This means it varies by platform, Rust version, andcan even differ within the same execution from one invocation to the next.This function currently corresponds to thecbrtf from libc on Unixand Windows. Note that this might change in the future.
§Examples
1.0.0 ·Sourcepub fnhypot(self, other:f32) ->f32
pub fnhypot(self, other:f32) ->f32
Compute the distance between the origin and a point (x,y) on theEuclidean plane. Equivalently, compute the length of the hypotenuse of aright-angle triangle with other sides having lengthx.abs() andy.abs().
§Unspecified precision
The precision of this function is non-deterministic. This means it varies by platform, Rust version, andcan even differ within the same execution from one invocation to the next.This function currently corresponds to thehypotf from libc on Unixand Windows. Note that this might change in the future.
§Examples
1.0.0 ·Sourcepub fnsin(self) ->f32
pub fnsin(self) ->f32
1.0.0 ·Sourcepub fncos(self) ->f32
pub fncos(self) ->f32
1.0.0 ·Sourcepub fntan(self) ->f32
pub fntan(self) ->f32
Computes the tangent of a number (in radians).
§Unspecified precision
The precision of this function is non-deterministic. This means it varies by platform, Rust version, andcan even differ within the same execution from one invocation to the next.This function currently corresponds to thetanf from libc on Unix andWindows. Note that this might change in the future.
§Examples
1.0.0 ·Sourcepub fnasin(self) ->f32
pub fnasin(self) ->f32
Computes the arcsine of a number. Return value is in radians inthe range [-pi/2, pi/2] or NaN if the number is outside the range[-1, 1].
§Unspecified precision
The precision of this function is non-deterministic. This means it varies by platform, Rust version, andcan even differ within the same execution from one invocation to the next.This function currently corresponds to theasinf from libc on Unixand Windows. Note that this might change in the future.
§Examples
1.0.0 ·Sourcepub fnacos(self) ->f32
pub fnacos(self) ->f32
Computes the arccosine of a number. Return value is in radians inthe range [0, pi] or NaN if the number is outside the range[-1, 1].
§Unspecified precision
The precision of this function is non-deterministic. This means it varies by platform, Rust version, andcan even differ within the same execution from one invocation to the next.This function currently corresponds to theacosf from libc on Unixand Windows. Note that this might change in the future.
§Examples
1.0.0 ·Sourcepub fnatan(self) ->f32
pub fnatan(self) ->f32
Computes the arctangent of a number. Return value is in radians in therange [-pi/2, pi/2];
§Unspecified precision
The precision of this function is non-deterministic. This means it varies by platform, Rust version, andcan even differ within the same execution from one invocation to the next.This function currently corresponds to theatanf from libc on Unixand Windows. Note that this might change in the future.
§Examples
1.0.0 ·Sourcepub fnatan2(self, other:f32) ->f32
pub fnatan2(self, other:f32) ->f32
Computes the four quadrant arctangent ofself (y) andother (x) in radians.
x = 0,y = 0:0x >= 0:arctan(y/x)->[-pi/2, pi/2]y >= 0:arctan(y/x) + pi->(pi/2, pi]y < 0:arctan(y/x) - pi->(-pi, -pi/2)
§Unspecified precision
The precision of this function is non-deterministic. This means it varies by platform, Rust version, andcan even differ within the same execution from one invocation to the next.This function currently corresponds to theatan2f from libc on Unixand Windows. Note that this might change in the future.
§Examples
// Positive angles measured counter-clockwise// from positive x axis// -pi/4 radians (45 deg clockwise)letx1 =3.0f32;lety1 = -3.0f32;// 3pi/4 radians (135 deg counter-clockwise)letx2 = -3.0f32;lety2 =3.0f32;letabs_difference_1 = (y1.atan2(x1) - (-std::f32::consts::FRAC_PI_4)).abs();letabs_difference_2 = (y2.atan2(x2) - (3.0* std::f32::consts::FRAC_PI_4)).abs();assert!(abs_difference_1 <=1e-5);assert!(abs_difference_2 <=1e-5);1.0.0 ·Sourcepub fnsin_cos(self) -> (f32,f32)
pub fnsin_cos(self) -> (f32,f32)
Simultaneously computes the sine and cosine of the number,x. Returns(sin(x), cos(x)).
§Unspecified precision
The precision of this function is non-deterministic. This means it varies by platform, Rust version, andcan even differ within the same execution from one invocation to the next.This function currently corresponds to the(f32::sin(x), f32::cos(x)). Note that this might change in the future.
§Examples
1.0.0 ·Sourcepub fnexp_m1(self) ->f32
pub fnexp_m1(self) ->f32
Returnse^(self) - 1 in a way that is accurate even if thenumber is close to zero.
§Unspecified precision
The precision of this function is non-deterministic. This means it varies by platform, Rust version, andcan even differ within the same execution from one invocation to the next.This function currently corresponds to theexpm1f from libc on Unixand Windows. Note that this might change in the future.
§Examples
1.0.0 ·Sourcepub fnln_1p(self) ->f32
pub fnln_1p(self) ->f32
Returnsln(1+n) (natural logarithm) more accurately than ifthe operations were performed separately.
This returns NaN whenn < -1.0, and negative infinity whenn == -1.0.
§Unspecified precision
The precision of this function is non-deterministic. This means it varies by platform, Rust version, andcan even differ within the same execution from one invocation to the next.This function currently corresponds to thelog1pf from libc on Unixand Windows. Note that this might change in the future.
§Examples
letx =1e-8_f32;// for very small x, ln(1 + x) is approximately x - x^2 / 2letapprox = x - x * x /2.0;letabs_difference = (x.ln_1p() - approx).abs();assert!(abs_difference <1e-10);Out-of-range values:
1.0.0 ·Sourcepub fnsinh(self) ->f32
pub fnsinh(self) ->f32
Hyperbolic sine function.
§Unspecified precision
The precision of this function is non-deterministic. This means it varies by platform, Rust version, andcan even differ within the same execution from one invocation to the next.This function currently corresponds to thesinhf from libc on Unixand Windows. Note that this might change in the future.
§Examples
1.0.0 ·Sourcepub fncosh(self) ->f32
pub fncosh(self) ->f32
Hyperbolic cosine function.
§Unspecified precision
The precision of this function is non-deterministic. This means it varies by platform, Rust version, andcan even differ within the same execution from one invocation to the next.This function currently corresponds to thecoshf from libc on Unixand Windows. Note that this might change in the future.
§Examples
1.0.0 ·Sourcepub fntanh(self) ->f32
pub fntanh(self) ->f32
Hyperbolic tangent function.
§Unspecified precision
The precision of this function is non-deterministic. This means it varies by platform, Rust version, andcan even differ within the same execution from one invocation to the next.This function currently corresponds to thetanhf from libc on Unixand Windows. Note that this might change in the future.
§Examples
1.0.0 ·Sourcepub fnasinh(self) ->f32
pub fnasinh(self) ->f32
1.0.0 ·Sourcepub fnacosh(self) ->f32
pub fnacosh(self) ->f32
1.0.0 ·Sourcepub fnatanh(self) ->f32
pub fnatanh(self) ->f32
Sourcepub fngamma(self) ->f32
🔬This is a nightly-only experimental API. (float_gamma #99842)
pub fngamma(self) ->f32
float_gamma #99842)Gamma function.
§Unspecified precision
The precision of this function is non-deterministic. This means it varies by platform, Rust version, andcan even differ within the same execution from one invocation to the next.This function currently corresponds to thetgammaf from libc on Unixand Windows. Note that this might change in the future.
§Examples
Sourcepub fnln_gamma(self) -> (f32,i32)
🔬This is a nightly-only experimental API. (float_gamma #99842)
pub fnln_gamma(self) -> (f32,i32)
float_gamma #99842)Natural logarithm of the absolute value of the gamma function
The integer part of the tuple indicates the sign of the gamma function.
§Unspecified precision
The precision of this function is non-deterministic. This means it varies by platform, Rust version, andcan even differ within the same execution from one invocation to the next.This function currently corresponds to thelgamma_r from libc on Unixand Windows. Note that this might change in the future.
§Examples
Sourcepub fnerf(self) ->f32
🔬This is a nightly-only experimental API. (float_erf #136321)
pub fnerf(self) ->f32
float_erf #136321)Error function.
§Unspecified precision
The precision of this function is non-deterministic. This means it varies by platform,Rust version, and can even differ within the same execution from one invocation to the next.
This function currently corresponds to theerff from libc on Unixand Windows. Note that this might change in the future.
§Examples
#![feature(float_erf)]/// The error function relates what percent of a normal distribution lies/// within `x` standard deviations (scaled by `1/sqrt(2)`).fnwithin_standard_deviations(x: f32) -> f32 { (x * std::f32::consts::FRAC_1_SQRT_2).erf() *100.0}// 68% of a normal distribution is within one standard deviationassert!((within_standard_deviations(1.0) -68.269).abs() <0.01);// 95% of a normal distribution is within two standard deviationsassert!((within_standard_deviations(2.0) -95.450).abs() <0.01);// 99.7% of a normal distribution is within three standard deviationsassert!((within_standard_deviations(3.0) -99.730).abs() <0.01);Sourcepub fnerfc(self) ->f32
🔬This is a nightly-only experimental API. (float_erf #136321)
pub fnerfc(self) ->f32
float_erf #136321)Complementary error function.
§Unspecified precision
The precision of this function is non-deterministic. This means it varies by platform,Rust version, and can even differ within the same execution from one invocation to the next.
This function currently corresponds to theerfcf from libc on Unixand Windows. Note that this might change in the future.
§Examples
Source§implf32
implf32
1.43.0 ·Sourcepub constMANTISSA_DIGITS:u32 = 24u32
pub constMANTISSA_DIGITS:u32 = 24u32
Number of significant digits in base 2.
Note that the size of the mantissa in the bitwise representation is onesmaller than this since the leading 1 is not stored explicitly.
1.43.0 ·Sourcepub constDIGITS:u32 = 6u32
pub constDIGITS:u32 = 6u32
Approximate number of significant digits in base 10.
This is the maximumx such that any decimal number withxsignificant digits can be converted tof32 and back without loss.
Equal to floor(log10 2MANTISSA_DIGITS − 1).
1.43.0 ·Sourcepub constEPSILON:f32 = 1.1920929E-7f32
pub constEPSILON:f32 = 1.1920929E-7f32
Machine epsilon value forf32.
This is the difference between1.0 and the next larger representable number.
Equal to 21 − MANTISSA_DIGITS.
1.43.0 ·Sourcepub constMIN_POSITIVE:f32 = 1.17549435E-38f32
pub constMIN_POSITIVE:f32 = 1.17549435E-38f32
Smallest positive normalf32 value.
Equal to 2MIN_EXP − 1.
1.43.0 ·Sourcepub constMAX:f32 = 3.40282347E+38f32
pub constMAX:f32 = 3.40282347E+38f32
Largest finitef32 value.
Equal to(1 − 2−MANTISSA_DIGITS) 2MAX_EXP.
1.43.0 ·Sourcepub constMIN_EXP:i32 = -125i32
pub constMIN_EXP:i32 = -125i32
One greater than the minimum possiblenormal power of 2 exponentfor a significand bounded by 1 ≤ x < 2 (i.e. the IEEE definition).
This corresponds to the exact minimum possiblenormal power of 2 exponentfor a significand bounded by 0.5 ≤ x < 1 (i.e. the C definition).In other words, all normal numbers representable by this type aregreater than or equal to 0.5 × 2MIN_EXP.
1.43.0 ·Sourcepub constMAX_EXP:i32 = 128i32
pub constMAX_EXP:i32 = 128i32
One greater than the maximum possible power of 2 exponentfor a significand bounded by 1 ≤ x < 2 (i.e. the IEEE definition).
This corresponds to the exact maximum possible power of 2 exponentfor a significand bounded by 0.5 ≤ x < 1 (i.e. the C definition).In other words, all numbers representable by this type arestrictly less than 2MAX_EXP.
1.43.0 ·Sourcepub constMIN_10_EXP:i32 = -37i32
pub constMIN_10_EXP:i32 = -37i32
Minimumx for which 10x is normal.
Equal to ceil(log10 MIN_POSITIVE).
1.43.0 ·Sourcepub constMAX_10_EXP:i32 = 38i32
pub constMAX_10_EXP:i32 = 38i32
Maximumx for which 10x is normal.
Equal to floor(log10 MAX).
1.43.0 ·Sourcepub constNAN:f32 = NaN_f32
pub constNAN:f32 = NaN_f32
Not a Number (NaN).
Note that IEEE 754 doesn’t define just a single NaN value; a plethora of bit patterns areconsidered to be NaN. Furthermore, the standard makes a difference between a “signaling” anda “quiet” NaN, and allows inspecting its “payload” (the unspecified bits in the bit pattern)and its sign. See thespecification of NaN bit patterns for moreinfo.
This constant is guaranteed to be a quiet NaN (on targets that follow the Rust assumptionsthat the quiet/signaling bit being set to 1 indicates a quiet NaN). Beyond that, nothing isguaranteed about the specific bit pattern chosen here: both payload and sign are arbitrary.The concrete bit pattern may change across Rust versions and target platforms.
1.43.0 ·Sourcepub constNEG_INFINITY:f32 = -Inf_f32
pub constNEG_INFINITY:f32 = -Inf_f32
Negative infinity (−∞).
1.0.0 (const: 1.83.0) ·Sourcepub const fnis_infinite(self) ->bool
pub const fnis_infinite(self) ->bool
1.53.0 (const: 1.83.0) ·Sourcepub const fnis_subnormal(self) ->bool
pub const fnis_subnormal(self) ->bool
Returnstrue if the number issubnormal.
letmin = f32::MIN_POSITIVE;// 1.17549435e-38f32letmax = f32::MAX;letlower_than_min =1.0e-40_f32;letzero =0.0_f32;assert!(!min.is_subnormal());assert!(!max.is_subnormal());assert!(!zero.is_subnormal());assert!(!f32::NAN.is_subnormal());assert!(!f32::INFINITY.is_subnormal());// Values between `0` and `min` are Subnormal.assert!(lower_than_min.is_subnormal());1.0.0 (const: 1.83.0) ·Sourcepub const fnis_normal(self) ->bool
pub const fnis_normal(self) ->bool
Returnstrue if the number is neither zero, infinite,subnormal, or NaN.
letmin = f32::MIN_POSITIVE;// 1.17549435e-38f32letmax = f32::MAX;letlower_than_min =1.0e-40_f32;letzero =0.0_f32;assert!(min.is_normal());assert!(max.is_normal());assert!(!zero.is_normal());assert!(!f32::NAN.is_normal());assert!(!f32::INFINITY.is_normal());// Values between `0` and `min` are Subnormal.assert!(!lower_than_min.is_normal());1.0.0 (const: 1.83.0) ·Sourcepub const fnclassify(self) ->FpCategory
pub const fnclassify(self) ->FpCategory
Returns the floating point category of the number. If only one propertyis going to be tested, it is generally faster to use the specificpredicate instead.
1.0.0 (const: 1.83.0) ·Sourcepub const fnis_sign_positive(self) ->bool
pub const fnis_sign_positive(self) ->bool
Returnstrue ifself has a positive sign, including+0.0, NaNs withpositive sign bit and positive infinity.
Note that IEEE 754 doesn’t assign any meaning to the sign bit in case ofa NaN, and as Rust doesn’t guarantee that the bit pattern of NaNs areconserved over arithmetic operations, the result ofis_sign_positive ona NaN might produce an unexpected or non-portable result. See thespecificationof NaN bit patterns for more info. Useself.signum() == 1.0if you need fully portable behavior (will returnfalse for all NaNs).
1.0.0 (const: 1.83.0) ·Sourcepub const fnis_sign_negative(self) ->bool
pub const fnis_sign_negative(self) ->bool
Returnstrue ifself has a negative sign, including-0.0, NaNs withnegative sign bit and negative infinity.
Note that IEEE 754 doesn’t assign any meaning to the sign bit in case ofa NaN, and as Rust doesn’t guarantee that the bit pattern of NaNs areconserved over arithmetic operations, the result ofis_sign_negative ona NaN might produce an unexpected or non-portable result. See thespecificationof NaN bit patterns for more info. Useself.signum() == -1.0if you need fully portable behavior (will returnfalse for all NaNs).
1.86.0 (const: 1.86.0) ·Sourcepub const fnnext_up(self) ->f32
pub const fnnext_up(self) ->f32
Returns the least number greater thanself.
LetTINY be the smallest representable positivef32. Then,
- if
self.is_nan(), this returnsself; - if
selfisNEG_INFINITY, this returnsMIN; - if
selfis-TINY, this returns -0.0; - if
selfis -0.0 or +0.0, this returnsTINY; - if
selfisMAXorINFINITY, this returnsINFINITY; - otherwise the unique least value greater than
selfis returned.
The identityx.next_up() == -(-x).next_down() holds for all non-NaNx. Whenxis finitex == x.next_up().next_down() also holds.
// f32::EPSILON is the difference between 1.0 and the next number up.assert_eq!(1.0f32.next_up(),1.0+ f32::EPSILON);// But not for most numbers.assert!(0.1f32.next_up() <0.1+ f32::EPSILON);assert_eq!(16777216f32.next_up(),16777218.0);This operation corresponds to IEEE-754nextUp.
1.86.0 (const: 1.86.0) ·Sourcepub const fnnext_down(self) ->f32
pub const fnnext_down(self) ->f32
Returns the greatest number less thanself.
LetTINY be the smallest representable positivef32. Then,
- if
self.is_nan(), this returnsself; - if
selfisINFINITY, this returnsMAX; - if
selfisTINY, this returns 0.0; - if
selfis -0.0 or +0.0, this returns-TINY; - if
selfisMINorNEG_INFINITY, this returnsNEG_INFINITY; - otherwise the unique greatest value less than
selfis returned.
The identityx.next_down() == -(-x).next_up() holds for all non-NaNx. Whenxis finitex == x.next_down().next_up() also holds.
letx =1.0f32;// Clamp value into range [0, 1).letclamped = x.clamp(0.0,1.0f32.next_down());assert!(clamped <1.0);assert_eq!(clamped.next_up(),1.0);This operation corresponds to IEEE-754nextDown.
1.7.0 (const: 1.85.0) ·Sourcepub const fnto_degrees(self) ->f32
pub const fnto_degrees(self) ->f32
1.7.0 (const: 1.85.0) ·Sourcepub const fnto_radians(self) ->f32
pub const fnto_radians(self) ->f32
1.0.0 (const: 1.85.0) ·Sourcepub const fnmax(self, other:f32) ->f32
pub const fnmax(self, other:f32) ->f32
Returns the maximum of the two numbers, ignoring NaN.
If one of the arguments is NaN, then the other argument is returned.This follows the IEEE 754-2008 semantics for maxNum, except for handling of signaling NaNs;this function handles all NaNs the same way and avoids maxNum’s problems with associativity.This also matches the behavior of libm’s fmax. In particular, if the inputs compare equal(such as for the case of+0.0 and-0.0), either input may be returned non-deterministically.
1.0.0 (const: 1.85.0) ·Sourcepub const fnmin(self, other:f32) ->f32
pub const fnmin(self, other:f32) ->f32
Returns the minimum of the two numbers, ignoring NaN.
If one of the arguments is NaN, then the other argument is returned.This follows the IEEE 754-2008 semantics for minNum, except for handling of signaling NaNs;this function handles all NaNs the same way and avoids minNum’s problems with associativity.This also matches the behavior of libm’s fmin. In particular, if the inputs compare equal(such as for the case of+0.0 and-0.0), either input may be returned non-deterministically.
Sourcepub const fnmaximum(self, other:f32) ->f32
🔬This is a nightly-only experimental API. (float_minimum_maximum #91079)
pub const fnmaximum(self, other:f32) ->f32
float_minimum_maximum #91079)Returns the maximum of the two numbers, propagating NaN.
This returns NaN wheneither argument is NaN, as opposed tof32::max which only returns NaN whenboth arguments are NaN.
#![feature(float_minimum_maximum)]letx =1.0f32;lety =2.0f32;assert_eq!(x.maximum(y), y);assert!(x.maximum(f32::NAN).is_nan());If one of the arguments is NaN, then NaN is returned. Otherwise this returns the greaterof the two numbers. For this operation, -0.0 is considered to be less than +0.0.Note that this follows the semantics specified in IEEE 754-2019.
Also note that “propagation” of NaNs here doesn’t necessarily mean that the bitpattern of a NaNoperand is conserved; see thespecification of NaN bit patterns for more info.
Sourcepub const fnminimum(self, other:f32) ->f32
🔬This is a nightly-only experimental API. (float_minimum_maximum #91079)
pub const fnminimum(self, other:f32) ->f32
float_minimum_maximum #91079)Returns the minimum of the two numbers, propagating NaN.
This returns NaN wheneither argument is NaN, as opposed tof32::min which only returns NaN whenboth arguments are NaN.
#![feature(float_minimum_maximum)]letx =1.0f32;lety =2.0f32;assert_eq!(x.minimum(y), x);assert!(x.minimum(f32::NAN).is_nan());If one of the arguments is NaN, then NaN is returned. Otherwise this returns the lesserof the two numbers. For this operation, -0.0 is considered to be less than +0.0.Note that this follows the semantics specified in IEEE 754-2019.
Also note that “propagation” of NaNs here doesn’t necessarily mean that the bitpattern of a NaNoperand is conserved; see thespecification of NaN bit patterns for more info.
1.85.0 (const: 1.85.0) ·Sourcepub const fnmidpoint(self, other:f32) ->f32
pub const fnmidpoint(self, other:f32) ->f32
Calculates the midpoint (average) betweenself andrhs.
This returns NaN wheneither argument is NaN or if a combination of+inf and -inf is provided as arguments.
§Examples
1.44.0 ·Sourcepub unsafe fnto_int_unchecked<Int>(self) -> Intwheref32:FloatToInt<Int>,
pub unsafe fnto_int_unchecked<Int>(self) -> Intwheref32:FloatToInt<Int>,
Rounds toward zero and converts to any primitive integer type,assuming that the value is finite and fits in that type.
letvalue =4.6_f32;letrounded =unsafe{ value.to_int_unchecked::<u16>() };assert_eq!(rounded,4);letvalue = -128.9_f32;letrounded =unsafe{ value.to_int_unchecked::<i8>() };assert_eq!(rounded, i8::MIN);§Safety
The value must:
- Not be
NaN - Not be infinite
- Be representable in the return type
Int, after truncating off its fractional part
1.20.0 (const: 1.83.0) ·Sourcepub const fnto_bits(self) ->u32
pub const fnto_bits(self) ->u32
Raw transmutation tou32.
This is currently identical totransmute::<f32, u32>(self) on all platforms.
Seefrom_bits for some discussion of theportability of this operation (there are almost no issues).
Note that this function is distinct fromas casting, which attempts topreserve thenumeric value, and not the bitwise value.
§Examples
1.20.0 (const: 1.83.0) ·Sourcepub const fnfrom_bits(v:u32) ->f32
pub const fnfrom_bits(v:u32) ->f32
Raw transmutation fromu32.
This is currently identical totransmute::<u32, f32>(v) on all platforms.It turns out this is incredibly portable, for two reasons:
- Floats and Ints have the same endianness on all supported platforms.
- IEEE 754 very precisely specifies the bit layout of floats.
However there is one caveat: prior to the 2008 version of IEEE 754, howto interpret the NaN signaling bit wasn’t actually specified. Most platforms(notably x86 and ARM) picked the interpretation that was ultimatelystandardized in 2008, but some didn’t (notably MIPS). As a result, allsignaling NaNs on MIPS are quiet NaNs on x86, and vice-versa.
Rather than trying to preserve signaling-ness cross-platform, thisimplementation favors preserving the exact bits. This means thatany payloads encoded in NaNs will be preserved even if the result ofthis method is sent over the network from an x86 machine to a MIPS one.
If the results of this method are only manipulated by the samearchitecture that produced them, then there is no portability concern.
If the input isn’t NaN, then there is no portability concern.
If you don’t care about signalingness (very likely), then there is noportability concern.
Note that this function is distinct fromas casting, which attempts topreserve thenumeric value, and not the bitwise value.
§Examples
1.40.0 (const: 1.83.0) ·Sourcepub const fnto_be_bytes(self) -> [u8;4]
pub const fnto_be_bytes(self) -> [u8;4]
1.40.0 (const: 1.83.0) ·Sourcepub const fnto_le_bytes(self) -> [u8;4]
pub const fnto_le_bytes(self) -> [u8;4]
1.40.0 (const: 1.83.0) ·Sourcepub const fnto_ne_bytes(self) -> [u8;4]
pub const fnto_ne_bytes(self) -> [u8;4]
Returns the memory representation of this floating point number as a byte array innative byte order.
As the target platform’s native endianness is used, portable codeshould useto_be_bytes orto_le_bytes, as appropriate, instead.
Seefrom_bits for some discussion of theportability of this operation (there are almost no issues).
§Examples
1.40.0 (const: 1.83.0) ·Sourcepub const fnfrom_be_bytes(bytes: [u8;4]) ->f32
pub const fnfrom_be_bytes(bytes: [u8;4]) ->f32
1.40.0 (const: 1.83.0) ·Sourcepub const fnfrom_le_bytes(bytes: [u8;4]) ->f32
pub const fnfrom_le_bytes(bytes: [u8;4]) ->f32
1.40.0 (const: 1.83.0) ·Sourcepub const fnfrom_ne_bytes(bytes: [u8;4]) ->f32
pub const fnfrom_ne_bytes(bytes: [u8;4]) ->f32
Creates a floating point value from its representation as a byte array in native endian.
As the target platform’s native endianness is used, portable codelikely wants to usefrom_be_bytes orfrom_le_bytes, asappropriate instead.
Seefrom_bits for some discussion of theportability of this operation (there are almost no issues).
§Examples
1.62.0 ·Sourcepub fntotal_cmp(&self, other: &f32) ->Ordering
pub fntotal_cmp(&self, other: &f32) ->Ordering
Returns the ordering betweenself andother.
Unlike the standard partial comparison between floating point numbers,this comparison always produces an ordering in accordance tothetotalOrder predicate as defined in the IEEE 754 (2008 revision)floating point standard. The values are ordered in the following sequence:
- negative quiet NaN
- negative signaling NaN
- negative infinity
- negative numbers
- negative subnormal numbers
- negative zero
- positive zero
- positive subnormal numbers
- positive numbers
- positive infinity
- positive signaling NaN
- positive quiet NaN.
The ordering established by this function does not always agree with thePartialOrd andPartialEq implementations off32. For example,they consider negative and positive zero equal, whiletotal_cmpdoesn’t.
The interpretation of the signaling NaN bit follows the definition inthe IEEE 754 standard, which may not match the interpretation by some ofthe older, non-conformant (e.g. MIPS) hardware implementations.
§Example
structGoodBoy { name: String, weight: f32,}letmutbois =vec![ GoodBoy { name:"Pucci".to_owned(), weight:0.1}, GoodBoy { name:"Woofer".to_owned(), weight:99.0}, GoodBoy { name:"Yapper".to_owned(), weight:10.0}, GoodBoy { name:"Chonk".to_owned(), weight: f32::INFINITY }, GoodBoy { name:"Abs. Unit".to_owned(), weight: f32::NAN }, GoodBoy { name:"Floaty".to_owned(), weight: -5.0},];bois.sort_by(|a, b| a.weight.total_cmp(&b.weight));// `f32::NAN` could be positive or negative, which will affect the sort order.iff32::NAN.is_sign_negative() {assert!(bois.into_iter().map(|b| b.weight) .zip([f32::NAN, -5.0,0.1,10.0,99.0, f32::INFINITY].iter()) .all(|(a, b)| a.to_bits() == b.to_bits()))}else{assert!(bois.into_iter().map(|b| b.weight) .zip([-5.0,0.1,10.0,99.0, f32::INFINITY, f32::NAN].iter()) .all(|(a, b)| a.to_bits() == b.to_bits()))}1.50.0 (const: 1.85.0) ·Sourcepub const fnclamp(self, min:f32, max:f32) ->f32
pub const fnclamp(self, min:f32, max:f32) ->f32
1.0.0 (const: 1.85.0) ·Sourcepub const fnabs(self) ->f32
pub const fnabs(self) ->f32
1.0.0 (const: 1.85.0) ·Sourcepub const fnsignum(self) ->f32
pub const fnsignum(self) ->f32
Returns a number that represents the sign ofself.
1.0if the number is positive,+0.0orINFINITY-1.0if the number is negative,-0.0orNEG_INFINITY- NaN if the number is NaN
§Examples
1.35.0 (const: 1.85.0) ·Sourcepub const fncopysign(self, sign:f32) ->f32
pub const fncopysign(self, sign:f32) ->f32
Returns a number composed of the magnitude ofself and the sign ofsign.
Equal toself if the sign ofself andsign are the same, otherwise equal to-self.Ifself is a NaN, then a NaN with the same payload asself and the sign bit ofsign isreturned.
Ifsign is a NaN, then this operation will still carry over its sign into the result. Notethat IEEE 754 doesn’t assign any meaning to the sign bit in case of a NaN, and as Rustdoesn’t guarantee that the bit pattern of NaNs are conserved over arithmetic operations, theresult ofcopysign withsign being a NaN might produce an unexpected or non-portableresult. See thespecification of NaN bit patterns for moreinfo.
§Examples
Sourcepub const fnalgebraic_add(self, rhs:f32) ->f32
🔬This is a nightly-only experimental API. (float_algebraic #136469)
pub const fnalgebraic_add(self, rhs:f32) ->f32
float_algebraic #136469)Float addition that allows optimizations based on algebraic rules.
Seealgebraic operators for more info.
Sourcepub const fnalgebraic_sub(self, rhs:f32) ->f32
🔬This is a nightly-only experimental API. (float_algebraic #136469)
pub const fnalgebraic_sub(self, rhs:f32) ->f32
float_algebraic #136469)Float subtraction that allows optimizations based on algebraic rules.
Seealgebraic operators for more info.
Sourcepub const fnalgebraic_mul(self, rhs:f32) ->f32
🔬This is a nightly-only experimental API. (float_algebraic #136469)
pub const fnalgebraic_mul(self, rhs:f32) ->f32
float_algebraic #136469)Float multiplication that allows optimizations based on algebraic rules.
Seealgebraic operators for more info.
Sourcepub const fnalgebraic_div(self, rhs:f32) ->f32
🔬This is a nightly-only experimental API. (float_algebraic #136469)
pub const fnalgebraic_div(self, rhs:f32) ->f32
float_algebraic #136469)Float division that allows optimizations based on algebraic rules.
Seealgebraic operators for more info.
Sourcepub const fnalgebraic_rem(self, rhs:f32) ->f32
🔬This is a nightly-only experimental API. (float_algebraic #136469)
pub const fnalgebraic_rem(self, rhs:f32) ->f32
float_algebraic #136469)Float remainder that allows optimizations based on algebraic rules.
Seealgebraic operators for more info.
Trait Implementations§
1.22.0 (const:unstable) ·Source§implAddAssign<&f32> forf32
implAddAssign<&f32> forf32
Source§fnadd_assign(&mut self, other: &f32)
fnadd_assign(&mut self, other: &f32)
+= operation.Read more1.8.0 (const:unstable) ·Source§implAddAssign forf32
implAddAssign forf32
Source§fnadd_assign(&mut self, other:f32)
fnadd_assign(&mut self, other:f32)
+= operation.Read more1.22.0 (const:unstable) ·Source§implDivAssign<&f32> forf32
implDivAssign<&f32> forf32
Source§fndiv_assign(&mut self, other: &f32)
fndiv_assign(&mut self, other: &f32)
/= operation.Read more1.8.0 (const:unstable) ·Source§implDivAssign forf32
implDivAssign forf32
Source§fndiv_assign(&mut self, other:f32)
fndiv_assign(&mut self, other:f32)
/= operation.Read more1.0.0 ·Source§implFromStr forf32
implFromStr forf32
Source§fnfrom_str(src: &str) ->Result<f32,ParseFloatError>
fnfrom_str(src: &str) ->Result<f32,ParseFloatError>
Converts a string in base 10 to a float.Accepts an optional decimal exponent.
This function accepts strings such as
- ‘3.14’
- ‘-3.14’
- ‘2.5E10’, or equivalently, ‘2.5e10’
- ‘2.5E-10’
- ‘5.’
- ‘.5’, or, equivalently, ‘0.5’
- ‘7’
- ‘007’
- ‘inf’, ‘-inf’, ‘+infinity’, ‘NaN’
Note that alphabetical characters are not case-sensitive.
Leading and trailing whitespace represent an error.
§Grammar
All strings that adhere to the followingEBNF grammar whenlowercased will result in anOk being returned:
Float ::= Sign? ( 'inf' | 'infinity' | 'nan' | Number )Number ::= ( Digit+ | Digit+ '.' Digit* | Digit* '.' Digit+ ) Exp?Exp ::= 'e' Sign? Digit+Sign ::= [+-]Digit ::= [0-9]§Arguments
- src - A string
§Return value
Err(ParseFloatError) if the string did not represent a validnumber. Otherwise,Ok(n) wheren is the closestrepresentable floating-point number to the number representedbysrc (following the same rules for rounding as for theresults of primitive operations).
Source§typeErr =ParseFloatError
typeErr =ParseFloatError
1.22.0 (const:unstable) ·Source§implMulAssign<&f32> forf32
implMulAssign<&f32> forf32
Source§fnmul_assign(&mut self, other: &f32)
fnmul_assign(&mut self, other: &f32)
*= operation.Read more1.8.0 (const:unstable) ·Source§implMulAssign forf32
implMulAssign forf32
Source§fnmul_assign(&mut self, other:f32)
fnmul_assign(&mut self, other:f32)
*= operation.Read more1.0.0 (const:unstable) ·Source§implPartialOrd forf32
implPartialOrd forf32
1.0.0 (const:unstable) ·Source§implRem forf32
The remainder from the division of two floats.
implRem forf32
The remainder from the division of two floats.
The remainder has the same sign as the dividend and is computed as:x - (x / y).trunc() * y.
§Examples
1.22.0 (const:unstable) ·Source§implRemAssign<&f32> forf32
implRemAssign<&f32> forf32
Source§fnrem_assign(&mut self, other: &f32)
fnrem_assign(&mut self, other: &f32)
%= operation.Read more1.8.0 (const:unstable) ·Source§implRemAssign forf32
implRemAssign forf32
Source§fnrem_assign(&mut self, other:f32)
fnrem_assign(&mut self, other:f32)
%= operation.Read moreSource§implSimdElement forf32
implSimdElement forf32
1.22.0 (const:unstable) ·Source§implSubAssign<&f32> forf32
implSubAssign<&f32> forf32
Source§fnsub_assign(&mut self, other: &f32)
fnsub_assign(&mut self, other: &f32)
-= operation.Read more1.8.0 (const:unstable) ·Source§implSubAssign forf32
implSubAssign forf32
Source§fnsub_assign(&mut self, other:f32)
fnsub_assign(&mut self, other:f32)
-= operation.Read more