c9d4ad07c4
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
29 lines
592 B
Rust
29 lines
592 B
Rust
extern mod extra;
|
|
|
|
use std::comm::Chan;
|
|
use std::task;
|
|
|
|
type RingBuffer = ~[f64];
|
|
type SamplesFn = ~fn(samples: &RingBuffer);
|
|
|
|
enum Msg
|
|
{
|
|
GetSamples(~str, SamplesFn), // sample set name, callback which receives samples
|
|
}
|
|
|
|
fn foo(name: ~str, samples_chan: Chan<Msg>) {
|
|
do task::spawn
|
|
{
|
|
let callback: SamplesFn =
|
|
|buffer|
|
|
{
|
|
for i in range(0u, buffer.len()) {
|
|
error2!("{}: {}", i, buffer[i])
|
|
}
|
|
};
|
|
samples_chan.send(GetSamples(name.clone(), callback));
|
|
};
|
|
}
|
|
|
|
pub fn main() {}
|