rust/tests/ui/statics/static-methods-in-traits2.rs

//@ run-pass
//@ pretty-expanded FIXME #23616

pub trait Number: NumConv {
    fn from<T:Number>(n: T) -> Self;
}

impl Number for f64 {
    fn from<T:Number>(n: T) -> f64 { n.to_float() }
}

pub trait NumConv {
    fn to_float(&self) -> f64;
}

impl NumConv for f64 {
    fn to_float(&self) -> f64 { *self }
}

pub fn main() {
    let _: f64 = Number::from(0.0f64);
}
Add `// run-pass` annotations to all the tests under `ui/run-pass/`. (I may have accidentally added it to some auxilliary crates as well; my emacs-macro-based methodology was pretty crude.) 2018-08-30 12:18:55 +00:00			`//@ run-pass`
rustdoc: Replace no-pretty-expanded with pretty-expanded Now that features must be declared expanded source often does not compile. This adds 'pretty-expanded' to a bunch of test cases that still work. 2015-03-22 20:13:15 +00:00			`//@ pretty-expanded FIXME #23616`

Fix vtable calculations when translating static methods. Closes #4165 2012-12-13 00:50:28 +00:00			`pub trait Number: NumConv {`
test: Remove `pure` from the test suite 2013-03-22 18:23:21 +00:00			`fn from<T:Number>(n: T) -> Self;`
Fix vtable calculations when translating static methods. Closes #4165 2012-12-13 00:50:28 +00:00			`}`

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 06:26:09 +00:00			`impl Number for f64 {`
			`fn from<T:Number>(n: T) -> f64 { n.to_float() }`
Fix vtable calculations when translating static methods. Closes #4165 2012-12-13 00:50:28 +00:00			`}`

			`pub trait NumConv {`
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 06:26:09 +00:00			`fn to_float(&self) -> f64;`
Fix vtable calculations when translating static methods. Closes #4165 2012-12-13 00:50:28 +00:00			`}`

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 06:26:09 +00:00			`impl NumConv for f64 {`
			`fn to_float(&self) -> f64 { *self }`
Fix vtable calculations when translating static methods. Closes #4165 2012-12-13 00:50:28 +00:00			`}`

check-fast fallout from removing export, r=burningtree 2013-02-02 03:43:17 +00: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 06:26:09 +00:00			`let _: f64 = Number::from(0.0f64);`
librustc: Change `self` as a type to `Self` everywhere. r=brson 2013-01-31 03:42:06 +00:00			`}`