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/test/debug-info/borrowed-unique-basic.rs | |
| parent | c8cdabc32fc7c6a5c3b01ef24340bc2f4b1ae359 (diff) | |
| parent | c9d4ad07c4c166d655f11862e03c10100dcb704b (diff) | |
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/test/debug-info/borrowed-unique-basic.rs')
| -rw-r--r-- | src/test/debug-info/borrowed-unique-basic.rs | 10 |
1 files changed, 2 insertions, 8 deletions
diff --git a/src/test/debug-info/borrowed-unique-basic.rs b/src/test/debug-info/borrowed-unique-basic.rs index ac295783c9f..48ac507b04d 100644 --- a/src/test/debug-info/borrowed-unique-basic.rs +++ b/src/test/debug-info/borrowed-unique-basic.rs @@ -51,14 +51,11 @@ // debugger:print *u64_ref // check:$12 = 64 -// debugger:print *float_ref -// check:$13 = 1.5 - // debugger:print *f32_ref -// check:$14 = 2.5 +// check:$13 = 2.5 // debugger:print *f64_ref -// check:$15 = 3.5 +// check:$14 = 3.5 #[allow(unused_variable)]; @@ -100,9 +97,6 @@ fn main() { let u64_box: ~u64 = ~64; let u64_ref: &u64 = u64_box; - let float_box: ~float = ~1.5; - let float_ref: &float = float_box; - let f32_box: ~f32 = ~2.5; let f32_ref: &f32 = f32_box; |
