Issue #8883 has been reported by melquiades (Paul Cantrell). ---------------------------------------- Bug #8883: Rational canonicalization unexpectedly converts to Fixnum https://bugs.ruby-lang.org/issues/8883 Author: melquiades (Paul Cantrell) Status: Open Priority: Normal Assignee: Category: core Target version: ruby -v: ruby 2.0.0p247 (2013-06-27 revision 41674) [x86_64-darwin12.3.0] Backport: 1.9.3: UNKNOWN, 2.0.0: UNKNOWN The documentation for Rational (http://www.ruby-doc.org/core-2.0.0/Rational.html) states that the result of creating or doing arithmetic on Rationals returns Rationals, as one would expect. Examples from the docs: Rational(1) #=> (1/1) 3.to_r #=> (3/1) Rational(-2, 9) * Rational(-9, 2) #=> (1/1) These all work as documented in 1.9. In 2.0, however, they all return Fixnum: Rational(1) #=> 1 3.to_r #=> 3 Rational(-2, 9) * Rational(-9, 2) #=> 1 This leads to unexpected behavior: Rational(2) / Rational(3) # => 0 ...but returns (2/3) in 1.9 That behavior is potentially dangerous. Math that may *usually* work, but suddenly start suffering from truncation errors depending on intermediate results. For example: def should_always_return_one(a, b, c) (Rational(a, c) + Rational(b, c)) / (a + b) * c end Under 1.9: should_always_return_one(2, 3, 7) #=> (1/1) should_always_return_one(2, 4, 7) #=> (1/1) should_always_return_one(2, 5, 7) #=> (1/1) should_always_return_one(2, 6, 7) #=> (1/1) Under 2.0: should_always_return_one(2, 3, 7) #=> 1 should_always_return_one(2, 4, 7) #=> 1 should_always_return_one(2, 5, 7) #=> 0 Oops! should_always_return_one(2, 6, 7) #=> 1 Either the docs are wrong, or this is a bug. I vote bug. Whether arithmetic expressions truncate the result should not depend on whether intermediate values just happen to be integers! Such behavior renders Rational almost too dangerous to use in situations where exact results are required. (Yes, I realize that requiring 'mathn' fixes this, but even with such a workaround as an option, this is dangerously broken. See also #2121.) Note that floating point arithmetic does _not_ exhibit this behavior.

on 2013-09-10 01:42

on 2013-09-10 03:12

Issue #8883 has been updated by phluid61 (Matthew Kerwin). =begin I can't reproduce this in any version of Ruby that I have installed. What is your Ruby 2.0 patch level? $ ruby2.0 -ve 'p Rational(2), Rational(3), Rational(2)/Rational(3)' ruby 2.0.0p247 (2013-06-27 revision 41674) [x86_64-linux] (2/1) (3/1) (2/3) $ ruby2.0 -ve 'p (Rational(2,7)+Rational(5,7))/((2+5)/7)' ruby 2.0.0p247 (2013-06-27 revision 41674) [x86_64-linux] (1/1) $ ruby2.1 -ve 'p (Rational(2,7)+Rational(5,7))/((2+5)/7)' ruby 2.1.0dev (2013-08-27 trunk 42696) [x86_64-linux] (1/1) $ ruby2.1 -ve 'p Rational(2), Rational(3), Rational(2)/Rational(3)' ruby 2.1.0dev (2013-08-27 trunk 42696) [x86_64-linux] (2/1) (3/1) (2/3) =end ---------------------------------------- Bug #8883: Rational canonicalization unexpectedly converts to Fixnum https://bugs.ruby-lang.org/issues/8883#change-41702 Author: melquiades (Paul Cantrell) Status: Open Priority: Normal Assignee: Category: core Target version: ruby -v: ruby 2.0.0p247 (2013-06-27 revision 41674) [x86_64-darwin12.3.0] Backport: 1.9.3: UNKNOWN, 2.0.0: UNKNOWN The documentation for Rational (http://www.ruby-doc.org/core-2.0.0/Rational.html) states that the result of creating or doing arithmetic on Rationals returns Rationals, as one would expect. Examples from the docs: Rational(1) #=> (1/1) 3.to_r #=> (3/1) Rational(-2, 9) * Rational(-9, 2) #=> (1/1) These all work as documented in 1.9. In 2.0, however, they all return Fixnum: Rational(1) #=> 1 3.to_r #=> 3 Rational(-2, 9) * Rational(-9, 2) #=> 1 This leads to unexpected behavior: Rational(2) / Rational(3) # => 0 ...but returns (2/3) in 1.9 That behavior is potentially dangerous. Math that may *usually* work, but suddenly start suffering from truncation errors depending on intermediate results. For example: def should_always_return_one(a, b, c) (Rational(a, c) + Rational(b, c)) / (a + b) * c end Under 1.9: should_always_return_one(2, 3, 7) #=> (1/1) should_always_return_one(2, 4, 7) #=> (1/1) should_always_return_one(2, 5, 7) #=> (1/1) should_always_return_one(2, 6, 7) #=> (1/1) Under 2.0: should_always_return_one(2, 3, 7) #=> 1 should_always_return_one(2, 4, 7) #=> 1 should_always_return_one(2, 5, 7) #=> 0 Oops! should_always_return_one(2, 6, 7) #=> 1 Either the docs are wrong, or this is a bug. I vote bug. Whether arithmetic expressions truncate the result should not depend on whether intermediate values just happen to be integers! Such behavior renders Rational almost too dangerous to use in situations where exact results are required. (Yes, I realize that requiring 'mathn' fixes this, but even with such a workaround as an option, this is dangerously broken. See also #2121.) Note that floating point arithmetic does _not_ exhibit this behavior.

on 2013-09-10 06:38

Issue #8883 has been updated by nobu (Nobuyoshi Nakada). Category changed from core to lib Rather, it is seems caused by mathn. $ ~/ruby/1.9.3/bin/ruby -e 'p Rational(2)*Rational(1,2)' (1/1) $ ~/ruby/1.9.3/bin/ruby -rmathn -e 'p Rational(2)*Rational(1,2)' 1 $ ~/ruby/2.0.0/bin/ruby -e 'p Rational(2)*Rational(1,2)' (1/1) $ ~/ruby/2.0.0/bin/ruby -rmathn -e 'p Rational(2)*Rational(1,2)' 1 ---------------------------------------- Bug #8883: Rational canonicalization unexpectedly converts to Fixnum https://bugs.ruby-lang.org/issues/8883#change-41707 Author: melquiades (Paul Cantrell) Status: Open Priority: Normal Assignee: Category: lib Target version: ruby -v: ruby 2.0.0p247 (2013-06-27 revision 41674) [x86_64-darwin12.3.0] Backport: 1.9.3: UNKNOWN, 2.0.0: UNKNOWN The documentation for Rational (http://www.ruby-doc.org/core-2.0.0/Rational.html) states that the result of creating or doing arithmetic on Rationals returns Rationals, as one would expect. Examples from the docs: Rational(1) #=> (1/1) 3.to_r #=> (3/1) Rational(-2, 9) * Rational(-9, 2) #=> (1/1) These all work as documented in 1.9. In 2.0, however, they all return Fixnum: Rational(1) #=> 1 3.to_r #=> 3 Rational(-2, 9) * Rational(-9, 2) #=> 1 This leads to unexpected behavior: Rational(2) / Rational(3) # => 0 ...but returns (2/3) in 1.9 That behavior is potentially dangerous. Math that may *usually* work, but suddenly start suffering from truncation errors depending on intermediate results. For example: def should_always_return_one(a, b, c) (Rational(a, c) + Rational(b, c)) / (a + b) * c end Under 1.9: should_always_return_one(2, 3, 7) #=> (1/1) should_always_return_one(2, 4, 7) #=> (1/1) should_always_return_one(2, 5, 7) #=> (1/1) should_always_return_one(2, 6, 7) #=> (1/1) Under 2.0: should_always_return_one(2, 3, 7) #=> 1 should_always_return_one(2, 4, 7) #=> 1 should_always_return_one(2, 5, 7) #=> 0 Oops! should_always_return_one(2, 6, 7) #=> 1 Either the docs are wrong, or this is a bug. I vote bug. Whether arithmetic expressions truncate the result should not depend on whether intermediate values just happen to be integers! Such behavior renders Rational almost too dangerous to use in situations where exact results are required. (Yes, I realize that requiring 'mathn' fixes this, but even with such a workaround as an option, this is dangerously broken. See also #2121.) Note that floating point arithmetic does _not_ exhibit this behavior.

on 2013-09-10 06:57

Issue #8883 has been updated by nobu (Nobuyoshi Nakada). Status changed from Open to Rejected Requiring only 'mathn/rational' causes this behavior. It's a bug to use 'mathn/rational' solely. ---------------------------------------- Bug #8883: Rational canonicalization unexpectedly converts to Fixnum https://bugs.ruby-lang.org/issues/8883#change-41708 Author: melquiades (Paul Cantrell) Status: Rejected Priority: Normal Assignee: Category: lib Target version: ruby -v: ruby 2.0.0p247 (2013-06-27 revision 41674) [x86_64-darwin12.3.0] Backport: 1.9.3: UNKNOWN, 2.0.0: UNKNOWN The documentation for Rational (http://www.ruby-doc.org/core-2.0.0/Rational.html) states that the result of creating or doing arithmetic on Rationals returns Rationals, as one would expect. Examples from the docs: Rational(1) #=> (1/1) 3.to_r #=> (3/1) Rational(-2, 9) * Rational(-9, 2) #=> (1/1) These all work as documented in 1.9. In 2.0, however, they all return Fixnum: Rational(1) #=> 1 3.to_r #=> 3 Rational(-2, 9) * Rational(-9, 2) #=> 1 This leads to unexpected behavior: Rational(2) / Rational(3) # => 0 ...but returns (2/3) in 1.9 That behavior is potentially dangerous. Math that may *usually* work, but suddenly start suffering from truncation errors depending on intermediate results. For example: def should_always_return_one(a, b, c) (Rational(a, c) + Rational(b, c)) / (a + b) * c end Under 1.9: should_always_return_one(2, 3, 7) #=> (1/1) should_always_return_one(2, 4, 7) #=> (1/1) should_always_return_one(2, 5, 7) #=> (1/1) should_always_return_one(2, 6, 7) #=> (1/1) Under 2.0: should_always_return_one(2, 3, 7) #=> 1 should_always_return_one(2, 4, 7) #=> 1 should_always_return_one(2, 5, 7) #=> 0 Oops! should_always_return_one(2, 6, 7) #=> 1 Either the docs are wrong, or this is a bug. I vote bug. Whether arithmetic expressions truncate the result should not depend on whether intermediate values just happen to be integers! Such behavior renders Rational almost too dangerous to use in situations where exact results are required. (Yes, I realize that requiring 'mathn' fixes this, but even with such a workaround as an option, this is dangerously broken. See also #2121.) Note that floating point arithmetic does _not_ exhibit this behavior.

on 2013-09-10 17:35

But your previous example required just mathn: $ ruby -rmathn -e 'p Rational(2,1)' 2 It seems like a mathn bug to me. Dave

on 2013-09-11 00:27

Issue #8883 has been updated by marcandre (Marc-Andre Lafortune). Status changed from Rejected to Open david_macmahon (David MacMahon) wrote: > But your previous example required just mathn: > > $ ruby -rmathn -e 'p Rational(2,1)' > 2 > > It seems like a mathn bug to me. Agreed. ---------------------------------------- Bug #8883: Rational canonicalization unexpectedly converts to Fixnum https://bugs.ruby-lang.org/issues/8883#change-41726 Author: melquiades (Paul Cantrell) Status: Open Priority: Normal Assignee: Category: lib Target version: ruby -v: ruby 2.0.0p247 (2013-06-27 revision 41674) [x86_64-darwin12.3.0] Backport: 1.9.3: UNKNOWN, 2.0.0: UNKNOWN The documentation for Rational (http://www.ruby-doc.org/core-2.0.0/Rational.html) states that the result of creating or doing arithmetic on Rationals returns Rationals, as one would expect. Examples from the docs: Rational(1) #=> (1/1) 3.to_r #=> (3/1) Rational(-2, 9) * Rational(-9, 2) #=> (1/1) These all work as documented in 1.9. In 2.0, however, they all return Fixnum: Rational(1) #=> 1 3.to_r #=> 3 Rational(-2, 9) * Rational(-9, 2) #=> 1 This leads to unexpected behavior: Rational(2) / Rational(3) # => 0 ...but returns (2/3) in 1.9 That behavior is potentially dangerous. Math that may *usually* work, but suddenly start suffering from truncation errors depending on intermediate results. For example: def should_always_return_one(a, b, c) (Rational(a, c) + Rational(b, c)) / (a + b) * c end Under 1.9: should_always_return_one(2, 3, 7) #=> (1/1) should_always_return_one(2, 4, 7) #=> (1/1) should_always_return_one(2, 5, 7) #=> (1/1) should_always_return_one(2, 6, 7) #=> (1/1) Under 2.0: should_always_return_one(2, 3, 7) #=> 1 should_always_return_one(2, 4, 7) #=> 1 should_always_return_one(2, 5, 7) #=> 0 Oops! should_always_return_one(2, 6, 7) #=> 1 Either the docs are wrong, or this is a bug. I vote bug. Whether arithmetic expressions truncate the result should not depend on whether intermediate values just happen to be integers! Such behavior renders Rational almost too dangerous to use in situations where exact results are required. (Yes, I realize that requiring 'mathn' fixes this, but even with such a workaround as an option, this is dangerously broken. See also #2121.) Note that floating point arithmetic does _not_ exhibit this behavior.

on 2013-09-11 00:28

Issue #8883 has been updated by marcandre (Marc-Andre Lafortune). Status changed from Open to Rejected Mmm, sorry, misread. I think the idea is that the buggy part (Rational(2) / Rational(3) # => 0) won't happen if you require 'mathn' ---------------------------------------- Bug #8883: Rational canonicalization unexpectedly converts to Fixnum https://bugs.ruby-lang.org/issues/8883#change-41727 Author: melquiades (Paul Cantrell) Status: Rejected Priority: Normal Assignee: Category: lib Target version: ruby -v: ruby 2.0.0p247 (2013-06-27 revision 41674) [x86_64-darwin12.3.0] Backport: 1.9.3: UNKNOWN, 2.0.0: UNKNOWN The documentation for Rational (http://www.ruby-doc.org/core-2.0.0/Rational.html) states that the result of creating or doing arithmetic on Rationals returns Rationals, as one would expect. Examples from the docs: Rational(1) #=> (1/1) 3.to_r #=> (3/1) Rational(-2, 9) * Rational(-9, 2) #=> (1/1) These all work as documented in 1.9. In 2.0, however, they all return Fixnum: Rational(1) #=> 1 3.to_r #=> 3 Rational(-2, 9) * Rational(-9, 2) #=> 1 This leads to unexpected behavior: Rational(2) / Rational(3) # => 0 ...but returns (2/3) in 1.9 That behavior is potentially dangerous. Math that may *usually* work, but suddenly start suffering from truncation errors depending on intermediate results. For example: def should_always_return_one(a, b, c) (Rational(a, c) + Rational(b, c)) / (a + b) * c end Under 1.9: should_always_return_one(2, 3, 7) #=> (1/1) should_always_return_one(2, 4, 7) #=> (1/1) should_always_return_one(2, 5, 7) #=> (1/1) should_always_return_one(2, 6, 7) #=> (1/1) Under 2.0: should_always_return_one(2, 3, 7) #=> 1 should_always_return_one(2, 4, 7) #=> 1 should_always_return_one(2, 5, 7) #=> 0 Oops! should_always_return_one(2, 6, 7) #=> 1 Either the docs are wrong, or this is a bug. I vote bug. Whether arithmetic expressions truncate the result should not depend on whether intermediate values just happen to be integers! Such behavior renders Rational almost too dangerous to use in situations where exact results are required. (Yes, I realize that requiring 'mathn' fixes this, but even with such a workaround as an option, this is dangerously broken. See also #2121.) Note that floating point arithmetic does _not_ exhibit this behavior.

on 2013-09-11 01:34

OK. I agree that requiring mathn avoids that buggy part. Thanks for clarifying. I guess I'm just a little uncomfortable with Rationals and Fixnums being promoted/demoted as needed, but maybe it's all OK and I'm just being paranoid. While playing around with this, I see that integer Floats also have some special handling: # Without mathn... $ ruby -e 'p [1/2.0, 1/2.5]' [0.5, 0.4] # With mathn... $ ruby -r mathn -e 'p [1/2.0, 1/2.5]' [(1/2), 0.4] Oddly though, this can result in non-reduced Rationals: $ ruby -r mathn -e 'p [2/2.0, 2/2.5]' [(2/2), 0.8] Weird. Also, why do integer Floats not get changed to Fixnums like Rational and Complex do? $ ruby -r mathn -e 'p Rational(1).class' Fixnum $ ruby -r mathn -e 'p Complex(1).class' Fixnum $ ruby -r mathn -e 'p Float(1).class' Float Thanks, Dave

on 2013-09-11 06:09

Issue #8883 has been updated by marcandre (Marc-Andre Lafortune). david_macmahon (David MacMahon) wrote: > While playing around with this, I see that integer Floats also have some special handling: Right. Floats are inexact while Integers & Rational are exact, and so are Complex with exact components. Rational(1/1) and 1 should yield the same mathematical result, but with floats that can be tricky. For example there are infinitely many different bigdecimals that will map to 1.0 (say 1.000....1 and 1.000...2 with enough zeros), but they don't behave exactly the same way, for example if you substract 1), so we can't freely map them. > Oddly though, this can result in non-reduced Rationals: > > $ ruby -r mathn -e 'p [2/2.0, 2/2.5]' > [(2/2), 0.8] Oh oh, that's a bug. It's not even related to 'mathn'. I opened a new issue about this: https://bugs.ruby-lang.org/issues/8894 ---------------------------------------- Bug #8883: Rational canonicalization unexpectedly converts to Fixnum https://bugs.ruby-lang.org/issues/8883#change-41732 Author: melquiades (Paul Cantrell) Status: Rejected Priority: Normal Assignee: Category: lib Target version: ruby -v: ruby 2.0.0p247 (2013-06-27 revision 41674) [x86_64-darwin12.3.0] Backport: 1.9.3: UNKNOWN, 2.0.0: UNKNOWN The documentation for Rational (http://www.ruby-doc.org/core-2.0.0/Rational.html) states that the result of creating or doing arithmetic on Rationals returns Rationals, as one would expect. Examples from the docs: Rational(1) #=> (1/1) 3.to_r #=> (3/1) Rational(-2, 9) * Rational(-9, 2) #=> (1/1) These all work as documented in 1.9. In 2.0, however, they all return Fixnum: Rational(1) #=> 1 3.to_r #=> 3 Rational(-2, 9) * Rational(-9, 2) #=> 1 This leads to unexpected behavior: Rational(2) / Rational(3) # => 0 ...but returns (2/3) in 1.9 That behavior is potentially dangerous. Math that may *usually* work, but suddenly start suffering from truncation errors depending on intermediate results. For example: def should_always_return_one(a, b, c) (Rational(a, c) + Rational(b, c)) / (a + b) * c end Under 1.9: should_always_return_one(2, 3, 7) #=> (1/1) should_always_return_one(2, 4, 7) #=> (1/1) should_always_return_one(2, 5, 7) #=> (1/1) should_always_return_one(2, 6, 7) #=> (1/1) Under 2.0: should_always_return_one(2, 3, 7) #=> 1 should_always_return_one(2, 4, 7) #=> 1 should_always_return_one(2, 5, 7) #=> 0 Oops! should_always_return_one(2, 6, 7) #=> 1 Either the docs are wrong, or this is a bug. I vote bug. Whether arithmetic expressions truncate the result should not depend on whether intermediate values just happen to be integers! Such behavior renders Rational almost too dangerous to use in situations where exact results are required. (Yes, I realize that requiring 'mathn' fixes this, but even with such a workaround as an option, this is dangerously broken. See also #2121.) Note that floating point arithmetic does _not_ exhibit this behavior.

on 2013-09-11 06:26

On Sep 10, 2013, at 9:09 PM, marcandre (Marc-Andre Lafortune) wrote: > > Issue #8883 has been updated by marcandre (Marc-Andre Lafortune). > > > david_macmahon (David MacMahon) wrote: >> While playing around with this, I see that integer Floats also have some special handling: > > Right. Floats are inexact while Integers & Rational are exact, and so are Complex with exact components. Rational(1/1) and 1 should yield the same mathematical result, but with floats that can be tricky. For example there are infinitely many different bigdecimals that will map to 1.0 (say 1.000....1 and 1.000...2 with enough zeros), but they don't behave exactly the same way, for example if you substract 1), so we can't freely map them. That's all fine from a numerical/mathematical point of view, but it still seems like there is something missing from the duck typing: $ ruby -e 'p (1/1.0).nan?' false $ ruby -r mathn -e 'p (1/1.1).nan?' false $ ruby -r mathn -e 'p (1/1.0).nan?' -e:1:in `<main>': undefined method `nan?' for (1/1):Rational (NoMethodError) Though admittedly this is getting a bit far from the OP. > >> Oddly though, this can result in non-reduced Rationals: >> >> $ ruby -r mathn -e 'p [2/2.0, 2/2.5]' >> [(2/2), 0.8] > > Oh oh, that's a bug. It's not even related to 'mathn'. I opened a new issue about this: https://bugs.ruby-lang.org/issues/8894 Thanks! Dave

on 2013-10-27 03:44

Issue #8883 has been updated by melquiades (Paul Cantrell). Somewhere in all the discussion, the actual bug got lost. This issue shouldn't be closed. To clarify: (1) The bug occurs when you do _not_ include mathn, and has nothing to do with mathn. (2) The bug occurs when you include _nothing_ at all: $ ~/.rvm/rubies/ruby-2.0.0-p247/bin/ruby -e 'p Rational(2) / Rational(3)' 0 That is clearly wrong. The should_always_return_one example demonstrates why this behavior is terribly dangerous, and is probably causing mathematically incorrect results in production code right now for poor unsuspecting souls out there in the world. (3) The bug does not occur in 1.9.3: $ ~/.rvm/rubies/ruby-1.9.3-p448/bin/ruby -e 'p Rational(2) / Rational(3)' (2/3) Bottom line: promoting the results of Rational calculations to Fixnum is never safe without mathn, not ever, and Ruby should never do it. ---------------------------------------- Bug #8883: Rational canonicalization unexpectedly converts to Fixnum https://bugs.ruby-lang.org/issues/8883#change-42630 Author: melquiades (Paul Cantrell) Status: Rejected Priority: Normal Assignee: Category: lib Target version: ruby -v: ruby 2.0.0p247 (2013-06-27 revision 41674) [x86_64-darwin12.3.0] Backport: 1.9.3: UNKNOWN, 2.0.0: UNKNOWN The documentation for Rational (http://www.ruby-doc.org/core-2.0.0/Rational.html) states that the result of creating or doing arithmetic on Rationals returns Rationals, as one would expect. Examples from the docs: Rational(1) #=> (1/1) 3.to_r #=> (3/1) Rational(-2, 9) * Rational(-9, 2) #=> (1/1) These all work as documented in 1.9. In 2.0, however, they all return Fixnum: Rational(1) #=> 1 3.to_r #=> 3 Rational(-2, 9) * Rational(-9, 2) #=> 1 This leads to unexpected behavior: Rational(2) / Rational(3) # => 0 ...but returns (2/3) in 1.9 That behavior is potentially dangerous. Math that may *usually* work, but suddenly start suffering from truncation errors depending on intermediate results. For example: def should_always_return_one(a, b, c) (Rational(a, c) + Rational(b, c)) / (a + b) * c end Under 1.9: should_always_return_one(2, 3, 7) #=> (1/1) should_always_return_one(2, 4, 7) #=> (1/1) should_always_return_one(2, 5, 7) #=> (1/1) should_always_return_one(2, 6, 7) #=> (1/1) Under 2.0: should_always_return_one(2, 3, 7) #=> 1 should_always_return_one(2, 4, 7) #=> 1 should_always_return_one(2, 5, 7) #=> 0 Oops! should_always_return_one(2, 6, 7) #=> 1 Either the docs are wrong, or this is a bug. I vote bug. Whether arithmetic expressions truncate the result should not depend on whether intermediate values just happen to be integers! Such behavior renders Rational almost too dangerous to use in situations where exact results are required. (Yes, I realize that requiring 'mathn' fixes this, but even with such a workaround as an option, this is dangerously broken. See also #2121.) Note that floating point arithmetic does _not_ exhibit this behavior.

on 2013-10-28 02:38

Issue #8883 has been updated by marcandre (Marc-Andre Lafortune). Hi melquiades (Paul Cantrell) wrote: > (2) The bug occurs when you include _nothing_ at all: > > $ ~/.rvm/rubies/ruby-2.0.0-p247/bin/ruby -e 'p Rational(2) / Rational(3)' > 0 I can't reproduce this, with ruby 2.0.0p247, p195 nor trunk. ---------------------------------------- Bug #8883: Rational canonicalization unexpectedly converts to Fixnum https://bugs.ruby-lang.org/issues/8883#change-42638 Author: melquiades (Paul Cantrell) Status: Rejected Priority: Normal Assignee: Category: lib Target version: ruby -v: ruby 2.0.0p247 (2013-06-27 revision 41674) [x86_64-darwin12.3.0] Backport: 1.9.3: UNKNOWN, 2.0.0: UNKNOWN The documentation for Rational (http://www.ruby-doc.org/core-2.0.0/Rational.html) states that the result of creating or doing arithmetic on Rationals returns Rationals, as one would expect. Examples from the docs: Rational(1) #=> (1/1) 3.to_r #=> (3/1) Rational(-2, 9) * Rational(-9, 2) #=> (1/1) These all work as documented in 1.9. In 2.0, however, they all return Fixnum: Rational(1) #=> 1 3.to_r #=> 3 Rational(-2, 9) * Rational(-9, 2) #=> 1 This leads to unexpected behavior: Rational(2) / Rational(3) # => 0 ...but returns (2/3) in 1.9 That behavior is potentially dangerous. Math that may *usually* work, but suddenly start suffering from truncation errors depending on intermediate results. For example: def should_always_return_one(a, b, c) (Rational(a, c) + Rational(b, c)) / (a + b) * c end Under 1.9: should_always_return_one(2, 3, 7) #=> (1/1) should_always_return_one(2, 4, 7) #=> (1/1) should_always_return_one(2, 5, 7) #=> (1/1) should_always_return_one(2, 6, 7) #=> (1/1) Under 2.0: should_always_return_one(2, 3, 7) #=> 1 should_always_return_one(2, 4, 7) #=> 1 should_always_return_one(2, 5, 7) #=> 0 Oops! should_always_return_one(2, 6, 7) #=> 1 Either the docs are wrong, or this is a bug. I vote bug. Whether arithmetic expressions truncate the result should not depend on whether intermediate values just happen to be integers! Such behavior renders Rational almost too dangerous to use in situations where exact results are required. (Yes, I realize that requiring 'mathn' fixes this, but even with such a workaround as an option, this is dangerously broken. See also #2121.) Note that floating point arithmetic does _not_ exhibit this behavior.

on 2013-10-28 04:48

Issue #8883 has been updated by nagachika (Tomoyuki Chikanaga). Hello, melquiades Don't you build your binary with --with-static-linked-ext ? A similar issue is reported when extension library mathn/rational is statically linked. See #8879 If so, require "mathn" explicitly ease the problem. ---------------------------------------- Bug #8883: Rational canonicalization unexpectedly converts to Fixnum https://bugs.ruby-lang.org/issues/8883#change-42639 Author: melquiades (Paul Cantrell) Status: Rejected Priority: Normal Assignee: Category: lib Target version: ruby -v: ruby 2.0.0p247 (2013-06-27 revision 41674) [x86_64-darwin12.3.0] Backport: 1.9.3: UNKNOWN, 2.0.0: UNKNOWN The documentation for Rational (http://www.ruby-doc.org/core-2.0.0/Rational.html) states that the result of creating or doing arithmetic on Rationals returns Rationals, as one would expect. Examples from the docs: Rational(1) #=> (1/1) 3.to_r #=> (3/1) Rational(-2, 9) * Rational(-9, 2) #=> (1/1) These all work as documented in 1.9. In 2.0, however, they all return Fixnum: Rational(1) #=> 1 3.to_r #=> 3 Rational(-2, 9) * Rational(-9, 2) #=> 1 This leads to unexpected behavior: Rational(2) / Rational(3) # => 0 ...but returns (2/3) in 1.9 That behavior is potentially dangerous. Math that may *usually* work, but suddenly start suffering from truncation errors depending on intermediate results. For example: def should_always_return_one(a, b, c) (Rational(a, c) + Rational(b, c)) / (a + b) * c end Under 1.9: should_always_return_one(2, 3, 7) #=> (1/1) should_always_return_one(2, 4, 7) #=> (1/1) should_always_return_one(2, 5, 7) #=> (1/1) should_always_return_one(2, 6, 7) #=> (1/1) Under 2.0: should_always_return_one(2, 3, 7) #=> 1 should_always_return_one(2, 4, 7) #=> 1 should_always_return_one(2, 5, 7) #=> 0 Oops! should_always_return_one(2, 6, 7) #=> 1 Either the docs are wrong, or this is a bug. I vote bug. Whether arithmetic expressions truncate the result should not depend on whether intermediate values just happen to be integers! Such behavior renders Rational almost too dangerous to use in situations where exact results are required. (Yes, I realize that requiring 'mathn' fixes this, but even with such a workaround as an option, this is dangerously broken. See also #2121.) Note that floating point arithmetic does _not_ exhibit this behavior.

on 2013-11-03 03:10

Issue #8883 has been updated by nobu (Nobuyoshi Nakada). Status changed from Rejected to Closed ---------------------------------------- Bug #8883: Rational canonicalization unexpectedly converts to Fixnum https://bugs.ruby-lang.org/issues/8883#change-42731 Author: melquiades (Paul Cantrell) Status: Closed Priority: Normal Assignee: Category: lib Target version: ruby -v: ruby 2.0.0p247 (2013-06-27 revision 41674) [x86_64-darwin12.3.0] Backport: 1.9.3: UNKNOWN, 2.0.0: UNKNOWN The documentation for Rational (http://www.ruby-doc.org/core-2.0.0/Rational.html) states that the result of creating or doing arithmetic on Rationals returns Rationals, as one would expect. Examples from the docs: Rational(1) #=> (1/1) 3.to_r #=> (3/1) Rational(-2, 9) * Rational(-9, 2) #=> (1/1) These all work as documented in 1.9. In 2.0, however, they all return Fixnum: Rational(1) #=> 1 3.to_r #=> 3 Rational(-2, 9) * Rational(-9, 2) #=> 1 This leads to unexpected behavior: Rational(2) / Rational(3) # => 0 ...but returns (2/3) in 1.9 That behavior is potentially dangerous. Math that may *usually* work, but suddenly start suffering from truncation errors depending on intermediate results. For example: def should_always_return_one(a, b, c) (Rational(a, c) + Rational(b, c)) / (a + b) * c end Under 1.9: should_always_return_one(2, 3, 7) #=> (1/1) should_always_return_one(2, 4, 7) #=> (1/1) should_always_return_one(2, 5, 7) #=> (1/1) should_always_return_one(2, 6, 7) #=> (1/1) Under 2.0: should_always_return_one(2, 3, 7) #=> 1 should_always_return_one(2, 4, 7) #=> 1 should_always_return_one(2, 5, 7) #=> 0 Oops! should_always_return_one(2, 6, 7) #=> 1 Either the docs are wrong, or this is a bug. I vote bug. Whether arithmetic expressions truncate the result should not depend on whether intermediate values just happen to be integers! Such behavior renders Rational almost too dangerous to use in situations where exact results are required. (Yes, I realize that requiring 'mathn' fixes this, but even with such a workaround as an option, this is dangerously broken. See also #2121.) Note that floating point arithmetic does _not_ exhibit this behavior.

on 2013-11-12 16:05

Issue #8883 has been updated by nagachika (Tomoyuki Chikanaga). Backport changed from 1.9.3: UNKNOWN, 2.0.0: UNKNOWN to 1.9.3: UNKNOWN, 2.0.0: DONE r43449, r43514 and r43525 are backported to ruby_2_0_0 at r43656. ---------------------------------------- Bug #8883: Rational canonicalization unexpectedly converts to Fixnum https://bugs.ruby-lang.org/issues/8883#change-42885 Author: melquiades (Paul Cantrell) Status: Closed Priority: Normal Assignee: Category: lib Target version: ruby -v: ruby 2.0.0p247 (2013-06-27 revision 41674) [x86_64-darwin12.3.0] Backport: 1.9.3: UNKNOWN, 2.0.0: DONE The documentation for Rational (http://www.ruby-doc.org/core-2.0.0/Rational.html) states that the result of creating or doing arithmetic on Rationals returns Rationals, as one would expect. Examples from the docs: Rational(1) #=> (1/1) 3.to_r #=> (3/1) Rational(-2, 9) * Rational(-9, 2) #=> (1/1) These all work as documented in 1.9. In 2.0, however, they all return Fixnum: Rational(1) #=> 1 3.to_r #=> 3 Rational(-2, 9) * Rational(-9, 2) #=> 1 This leads to unexpected behavior: Rational(2) / Rational(3) # => 0 ...but returns (2/3) in 1.9 That behavior is potentially dangerous. Math that may *usually* work, but suddenly start suffering from truncation errors depending on intermediate results. For example: def should_always_return_one(a, b, c) (Rational(a, c) + Rational(b, c)) / (a + b) * c end Under 1.9: should_always_return_one(2, 3, 7) #=> (1/1) should_always_return_one(2, 4, 7) #=> (1/1) should_always_return_one(2, 5, 7) #=> (1/1) should_always_return_one(2, 6, 7) #=> (1/1) Under 2.0: should_always_return_one(2, 3, 7) #=> 1 should_always_return_one(2, 4, 7) #=> 1 should_always_return_one(2, 5, 7) #=> 0 Oops! should_always_return_one(2, 6, 7) #=> 1 Either the docs are wrong, or this is a bug. I vote bug. Whether arithmetic expressions truncate the result should not depend on whether intermediate values just happen to be integers! Such behavior renders Rational almost too dangerous to use in situations where exact results are required. (Yes, I realize that requiring 'mathn' fixes this, but even with such a workaround as an option, this is dangerously broken. See also #2121.) Note that floating point arithmetic does _not_ exhibit this behavior.

on 2013-11-19 08:44

Issue #8883 has been updated by melquiades (Paul Cantrell). @nagachika: Yes, your guess is correct. I am using rvm, which passes --with-static-linked-ext. I verified that patch 43656 does indeed fix the issue: $ rvm install 2.0.0-patch43656 --patch changeset_r43656.diff ... ~/.rvm/rubies/ruby-2.0.0-p247-patch43656/bin/ruby -e 'p Rational(2) / Rational(3)' (2/3) Hooray! (Apologies for my slow responses. Apparently I'm not receiving email notifications on this thread, despite having watched it.) ---------------------------------------- Bug #8883: Rational canonicalization unexpectedly converts to Fixnum https://bugs.ruby-lang.org/issues/8883#change-43016 Author: melquiades (Paul Cantrell) Status: Closed Priority: Normal Assignee: Category: lib Target version: ruby -v: ruby 2.0.0p247 (2013-06-27 revision 41674) [x86_64-darwin12.3.0] Backport: 1.9.3: UNKNOWN, 2.0.0: DONE The documentation for Rational (http://www.ruby-doc.org/core-2.0.0/Rational.html) states that the result of creating or doing arithmetic on Rationals returns Rationals, as one would expect. Examples from the docs: Rational(1) #=> (1/1) 3.to_r #=> (3/1) Rational(-2, 9) * Rational(-9, 2) #=> (1/1) These all work as documented in 1.9. In 2.0, however, they all return Fixnum: Rational(1) #=> 1 3.to_r #=> 3 Rational(-2, 9) * Rational(-9, 2) #=> 1 This leads to unexpected behavior: Rational(2) / Rational(3) # => 0 ...but returns (2/3) in 1.9 That behavior is potentially dangerous. Math that may *usually* work, but suddenly start suffering from truncation errors depending on intermediate results. For example: def should_always_return_one(a, b, c) (Rational(a, c) + Rational(b, c)) / (a + b) * c end Under 1.9: should_always_return_one(2, 3, 7) #=> (1/1) should_always_return_one(2, 4, 7) #=> (1/1) should_always_return_one(2, 5, 7) #=> (1/1) should_always_return_one(2, 6, 7) #=> (1/1) Under 2.0: should_always_return_one(2, 3, 7) #=> 1 should_always_return_one(2, 4, 7) #=> 1 should_always_return_one(2, 5, 7) #=> 0 Oops! should_always_return_one(2, 6, 7) #=> 1 Either the docs are wrong, or this is a bug. I vote bug. Whether arithmetic expressions truncate the result should not depend on whether intermediate values just happen to be integers! Such behavior renders Rational almost too dangerous to use in situations where exact results are required. (Yes, I realize that requiring 'mathn' fixes this, but even with such a workaround as an option, this is dangerously broken. See also #2121.) Note that floating point arithmetic does _not_ exhibit this behavior.