diff options
| author | bors <bors@rust-lang.org> | 2013-10-01 13:01:28 -0700 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2013-10-01 13:01:28 -0700 |
| commit | 08b510c351e990d835511f45a28f2f29c12ee545 (patch) | |
| tree | 41b6f0afad8fac043f3985c2a842dfde27e2b745 /src/libstd/fmt | |
| parent | c8cdabc32fc7c6a5c3b01ef24340bc2f4b1ae359 (diff) | |
| parent | c9d4ad07c4c166d655f11862e03c10100dcb704b (diff) | |
| download | rust-08b510c351e990d835511f45a28f2f29c12ee545.tar.gz rust-08b510c351e990d835511f45a28f2f29c12ee545.zip | |
auto merge of #9519 : thestinger/rust/float, r=catamorphism
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/fmt')
| -rw-r--r-- | src/libstd/fmt/mod.rs | 2 |
1 files changed, 0 insertions, 2 deletions
diff --git a/src/libstd/fmt/mod.rs b/src/libstd/fmt/mod.rs index ba3a3bb4cc8..a03f21d69c8 100644 --- a/src/libstd/fmt/mod.rs +++ b/src/libstd/fmt/mod.rs @@ -1035,7 +1035,6 @@ macro_rules! floating(($ty:ident) => { } } }) -floating!(float) floating!(f32) floating!(f64) @@ -1096,7 +1095,6 @@ delegate!(~str to String) delegate!(&'self str to String) delegate!(bool to Bool) delegate!(char to Char) -delegate!(float to Float) delegate!(f32 to Float) delegate!(f64 to Float) |