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

1 files changed, 0 insertions, 9 deletions

diff --git a/src/libextra/ebml.rs b/src/libextra/ebml.rs
index 8cba1a417d0..0792400e857 100644
--- a/src/libextra/ebml.rs
+++ b/src/libextra/ebml.rs
@@ -422,10 +422,6 @@ pub mod reader {
             let bits = doc_as_u32(self.next_doc(EsF32));
             unsafe { transmute(bits) }
         }
-        fn read_float(&mut self) -> float {
-            let bits = doc_as_u64(self.next_doc(EsFloat));
-            (unsafe { transmute::<u64, f64>(bits) }) as float
-        }
         fn read_char(&mut self) -> char {
             char::from_u32(doc_as_u32(self.next_doc(EsChar))).unwrap()
         }
@@ -839,11 +835,6 @@ pub mod writer {
             let bits = unsafe { cast::transmute(v) };
             self.wr_tagged_u32(EsF32 as uint, bits);
         }
-        fn emit_float(&mut self, v: float) {
-            let bits = unsafe { cast::transmute(v as f64) };
-            self.wr_tagged_u64(EsFloat as uint, bits);
-        }
-
         fn emit_char(&mut self, v: char) {
             self.wr_tagged_u32(EsChar as uint, v as u32);
         }