diff options
| author | Daniel Micay <danielmicay@gmail.com> | 2013-09-26 02:26:09 -0400 |
|---|---|---|
| committer | Daniel Micay <danielmicay@gmail.com> | 2013-10-01 14:54:10 -0400 |
| commit | c9d4ad07c4c166d655f11862e03c10100dcb704b (patch) | |
| tree | 53a506f27ce5d9e192ef540ae3ad4010eba10fee /src/libstd/to_bytes.rs | |
| parent | 24a253778aa26222cae97e3b57f85e5054a39977 (diff) | |
remove the `float` type
It is simply defined as `f64` across every platform right now. A use case hasn't been presented for a `float` type defined as the highest precision floating point type implemented in hardware on the platform. Performance-wise, using the smallest precision correct for the use case greatly saves on cache space and allows for fitting more numbers into SSE/AVX registers. If there was a use case, this could be implemented as simply a type alias or a struct thanks to `#[cfg(...)]`. Closes #6592 The mailing list thread, for reference: https://mail.mozilla.org/pipermail/rust-dev/2013-July/004632.html
Diffstat (limited to 'src/libstd/to_bytes.rs')
| -rw-r--r-- | src/libstd/to_bytes.rs | 7 |
1 files changed, 0 insertions, 7 deletions
diff --git a/src/libstd/to_bytes.rs b/src/libstd/to_bytes.rs index f47468e1ef8..4d5da19dafd 100644 --- a/src/libstd/to_bytes.rs +++ b/src/libstd/to_bytes.rs @@ -198,13 +198,6 @@ impl IterBytes for int { } } -impl IterBytes for float { - #[inline] - fn iter_bytes(&self, lsb0: bool, f: Cb) -> bool { - (*self as f64).iter_bytes(lsb0, f) - } -} - impl IterBytes for f32 { #[inline] fn iter_bytes(&self, lsb0: bool, f: Cb) -> bool { |