rust/src/test/run-pass/static-fn-trait-xc.rs

// aux-build:static_fn_trait_xc_aux.rs
// xfail-fast

extern mod mycore(name ="static_fn_trait_xc_aux");

use mycore::num;

pub fn main() {
    let _1: f64 = num::Num2::from_int2(1i);
}
Fix encoding of trait static method paths. Closes #4097. r=pcwalton 2012-12-13 16:55:08 -06:00			`// aux-build:static_fn_trait_xc_aux.rs`
Update src/test/run-pass/static-fn-trait-xc.rs 2012-12-13 23:17:11 -06:00			`// xfail-fast`
Fix encoding of trait static method paths. Closes #4097. r=pcwalton 2012-12-13 16:55:08 -06:00
			`extern mod mycore(name ="static_fn_trait_xc_aux");`

test: Fix botched regex. rs=bustage 2013-01-08 12:35:20 -06:00			`use mycore::num;`
Fix encoding of trait static method paths. Closes #4097. r=pcwalton 2012-12-13 16:55:08 -06:00
check-fast fallout from removing export, r=burningtree 2013-02-01 21:43:17 -06:00			`pub fn main() {`
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 2013-09-26 01:26:09 -05:00			`let _1: f64 = num::Num2::from_int2(1i);`
Fix encoding of trait static method paths. Closes #4097. r=pcwalton 2012-12-13 16:55:08 -06:00			`}`