diff options
| author | Brendan Zabarauskas <bjzaba@yahoo.com.au> | 2014-01-08 22:57:31 +1100 |
|---|---|---|
| committer | Brendan Zabarauskas <bjzaba@yahoo.com.au> | 2014-01-09 15:41:46 +1100 |
| commit | ceea85a148ec3426edfc00b8353a19c1d2df5dbf (patch) | |
| tree | 34005cf06fde432a44cff41aca0a6603b12cf3a4 /doc | |
| parent | 7613b15fdbbb9bf770a2c731f4135886b0ff3cf0 (diff) | |
| download | rust-ceea85a148ec3426edfc00b8353a19c1d2df5dbf.tar.gz rust-ceea85a148ec3426edfc00b8353a19c1d2df5dbf.zip | |
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.
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/guide-testing.md | 3 |
1 files changed, 1 insertions, 2 deletions
diff --git a/doc/guide-testing.md b/doc/guide-testing.md index b56cea12273..eeed3c7d9a7 100644 --- a/doc/guide-testing.md +++ b/doc/guide-testing.md @@ -48,8 +48,7 @@ value. To run the tests in a crate, it must be compiled with the the resulting executable will run all the tests in the crate. A test is considered successful if its function returns; if the task running the test fails, through a call to `fail!`, a failed `check` or -`assert`, or some other (`assert_eq`, `assert_approx_eq`, ...) means, -then the test fails. +`assert`, or some other (`assert_eq`, ...) means, then the test fails. When compiling a crate with the '--test' flag '--cfg test' is also implied, so that tests can be conditionally compiled. |