<feed xmlns='http://www.w3.org/2005/Atom'>
<title>rust/src/test/run-fail/assert-approx-eq-eps-macro-fail.rs, branch 0.9</title>
<subtitle>https://github.com/rust-lang/rust
</subtitle>
<id>http://git.dreamy.place/mirrors/rust/atom?h=0.9</id>
<link rel='self' href='http://git.dreamy.place/mirrors/rust/atom?h=0.9'/>
<link rel='alternate' type='text/html' href='http://git.dreamy.place/mirrors/rust/'/>
<updated>2013-10-01T18:54:10+00:00</updated>
<entry>
<title>remove the `float` type</title>
<updated>2013-10-01T18:54:10+00:00</updated>
<author>
<name>Daniel Micay</name>
<email>danielmicay@gmail.com</email>
</author>
<published>2013-09-26T06:26:09+00:00</published>
<link rel='alternate' type='text/html' href='http://git.dreamy.place/mirrors/rust/commit/?id=c9d4ad07c4c166d655f11862e03c10100dcb704b'/>
<id>urn:sha1:c9d4ad07c4c166d655f11862e03c10100dcb704b</id>
<content type='text'>
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
</content>
</entry>
<entry>
<title>Add assert_approx_eq! macro</title>
<updated>2013-05-06T11:51:48+00:00</updated>
<author>
<name>Brendan Zabarauskas</name>
<email>bjzaba@yahoo.com.au</email>
</author>
<published>2013-05-06T11:51:48+00:00</published>
<link rel='alternate' type='text/html' href='http://git.dreamy.place/mirrors/rust/commit/?id=0e2242f6d62d6d49bf8a2d1860a41273c1fdfa0d'/>
<id>urn:sha1:0e2242f6d62d6d49bf8a2d1860a41273c1fdfa0d</id>
<content type='text'>
</content>
</entry>
</feed>
