about summary refs log tree commit diff
path: root/src/libstd/iter.rs
diff options
context:
space:
mode:
authorDaniel Micay <danielmicay@gmail.com>2013-09-26 02:26:09 -0400
committerDaniel Micay <danielmicay@gmail.com>2013-10-01 14:54:10 -0400
commitc9d4ad07c4c166d655f11862e03c10100dcb704b (patch)
tree53a506f27ce5d9e192ef540ae3ad4010eba10fee /src/libstd/iter.rs
parent24a253778aa26222cae97e3b57f85e5054a39977 (diff)
downloadrust-c9d4ad07c4c166d655f11862e03c10100dcb704b.tar.gz
rust-c9d4ad07c4c166d655f11862e03c10100dcb704b.zip
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/iter.rs')
-rw-r--r--src/libstd/iter.rs6
1 files changed, 3 insertions, 3 deletions
diff --git a/src/libstd/iter.rs b/src/libstd/iter.rs
index f1e0eff5616..6043f7e3f52 100644
--- a/src/libstd/iter.rs
+++ b/src/libstd/iter.rs
@@ -2269,12 +2269,12 @@ mod tests {
     #[test]
     fn test_iterator_scan() {
         // test the type inference
-        fn add(old: &mut int, new: &uint) -> Option<float> {
+        fn add(old: &mut int, new: &uint) -> Option<f64> {
             *old += *new as int;
-            Some(*old as float)
+            Some(*old as f64)
         }
         let xs = [0u, 1, 2, 3, 4];
-        let ys = [0f, 1f, 3f, 6f, 10f];
+        let ys = [0f64, 1.0, 3.0, 6.0, 10.0];
 
         let mut it = xs.iter().scan(0, add);
         let mut i = 0;