mikros/rust
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
393ce1820e
rust/src/libstd/num/float_macros.rs

22 lines
752 B
Rust
Raw Normal View History

Remove ApproxEq and assert_approx_eq! This trait seems to stray too far from the mandate of a standard library as implementations may vary between use cases.
2014-01-08 05:57:31 -06:00
// Copyright 2014 The Rust Project Developers. See the COPYRIGHT
Add assert_approx_eq! macro
2013-05-06 06:51:48 -05:00
// file at the top-level directory of this distribution and at
// http://rust-lang.org/COPYRIGHT.
//
// Licensed under the Apache License, Version 2.0 <LICENSE-APACHE or
// http://www.apache.org/licenses/LICENSE-2.0> or the MIT license
// <LICENSE-MIT or http://opensource.org/licenses/MIT>, at your
// option. This file may not be copied, modified, or distributed
// except according to those terms.
Set unstable feature names appropriately * `core` - for the core crate * `hash` - hashing * `io` - io * `path` - path * `alloc` - alloc crate * `rand` - rand crate * `collections` - collections crate * `std_misc` - other parts of std * `test` - test crate * `rustc_private` - everything else
2015-01-22 20:22:03 -06:00
#![unstable(feature = "std_misc")]
Convert most code to new inner attribute syntax. Closes #2569
2014-03-21 20:05:05 -05:00
#![doc(hidden)]
Remove ApproxEq and assert_approx_eq! This trait seems to stray too far from the mandate of a standard library as implementations may vary between use cases.
2014-01-08 05:57:31 -06:00
librustc: Always parse `macro!()`/`macro![]` as expressions if not followed by a semicolon. This allows code like `vec![1i, 2, 3].len();` to work. This breaks code that uses macros as statements without putting semicolons after them, such as: fn main() { ... assert!(a == b) assert!(c == d) println(...); } It also breaks code that uses macros as items without semicolons: local_data_key!(foo) fn main() { println("hello world") } Add semicolons to fix this code. Those two examples can be fixed as follows: fn main() { ... assert!(a == b); assert!(c == d); println(...); } local_data_key!(foo); fn main() { println("hello world") } RFC #378. Closes #18635. [breaking-change]
2014-11-14 11:18:10 -06:00
macro_rules! assert_approx_eq {
Remove ApproxEq and assert_approx_eq! This trait seems to stray too far from the mandate of a standard library as implementations may vary between use cases.
2014-01-08 05:57:31 -06:00
($a:expr, $b:expr) => ({
Remove Signed trait and add SignedInt trait The methods have been moved into Float and SignedInt
2014-11-12 07:02:42 -06:00
use num::Float;
Remove ApproxEq and assert_approx_eq! This trait seems to stray too far from the mandate of a standard library as implementations may vary between use cases.
2014-01-08 05:57:31 -06:00
let (a, b) = (&$a, &$b);
assert!((*a - *b).abs() < 1.0e-6,
"{} is not approximately equal to {}", *a, *b);
})
librustc: Always parse `macro!()`/`macro![]` as expressions if not followed by a semicolon. This allows code like `vec![1i, 2, 3].len();` to work. This breaks code that uses macros as statements without putting semicolons after them, such as: fn main() { ... assert!(a == b) assert!(c == d) println(...); } It also breaks code that uses macros as items without semicolons: local_data_key!(foo) fn main() { println("hello world") } Add semicolons to fix this code. Those two examples can be fixed as follows: fn main() { ... assert!(a == b); assert!(c == d); println(...); } local_data_key!(foo); fn main() { println("hello world") } RFC #378. Closes #18635. [breaking-change]
2014-11-14 11:18:10 -06:00
}
Reference in New Issue Copy Permalink