diff options
| author | KOBAYASHI Shuji <[email protected]> | 2019-03-26 22:12:09 +0900 |
|---|---|---|
| committer | KOBAYASHI Shuji <[email protected]> | 2019-03-26 22:12:09 +0900 |
| commit | 0b6696cc2872c9b33efa48c7dcd45dc4a17f3686 (patch) | |
| tree | 3718e369517fd3dca7be81364e0b4fdf72a4c18f /src/debug.c | |
| parent | c2660b8111cd6cd98a41aa257c503cbd3a7cf881 (diff) | |
| download | mruby-0b6696cc2872c9b33efa48c7dcd45dc4a17f3686.tar.gz mruby-0b6696cc2872c9b33efa48c7dcd45dc4a17f3686.zip | |
Fix dealing with infinity and NaN in `test/assert.rb:assert_float`
`assert_float` is always passed when expected value and/or actual value are
infinity or NaN. This behavior seems unintentional.
Before this patch:
assert_float(Float::INFINITY, 1.0) #=> pass
assert_float(-Float::INFINITY, 1) #=> pass
assert_float(1, 1/0) #=> pass
assert_float(1, -1/0) #=> pass
assert_float(1.0, Float::NAN) #=> pass
assert_float(Float::NAN, 1) #=> pass
After this patch:
assert_float(Float::INFINITY, 1.0) #=> fail: Expected 1.0 to be Infinity.
assert_float(-Float::INFINITY, 1) #=> fail: Expected 1 to be -Infinity.
assert_float(1, 1/0) #=> fail: Expected Infinity to be 1.
assert_float(1, -1/0) #=> fail: Expected -Infinity to be 1.
assert_float(1.0, Float::NAN) #=> fail: Expected NaN to be 1.0.
assert_float(Float::NAN, 1) #=> fail: Expected 1 to be NaN.
Diffstat (limited to 'src/debug.c')
0 files changed, 0 insertions, 0 deletions
