https://bugs.ruby-lang.org/https://bugs.ruby-lang.org/favicon.ico?17113305112013-09-03T13:23:16ZRuby Issue Tracking SystemRuby master - Bug #8826: BigDecimal#div and #quo different behavior and inconsistencieshttps://bugs.ruby-lang.org/issues/8826?journal_id=415532013-09-03T13:23:16Zzzak (zzak _)
<ul><li><strong>Category</strong> set to <i>ext</i></li><li><strong>Status</strong> changed from <i>Open</i> to <i>Assigned</i></li><li><strong>Assignee</strong> set to <i>mrkn (Kenta Murata)</i></li></ul><p>The documentation for BigDecimal#div is aliases under #quo, sorry for the confusion. I will fix this!</p>
<p><a class="user active user-mention" href="https://bugs.ruby-lang.org/users/482">@mrkn (Kenta Murata)</a> Can you also comment?</p> Ruby master - Bug #8826: BigDecimal#div and #quo different behavior and inconsistencieshttps://bugs.ruby-lang.org/issues/8826?journal_id=619622016-12-10T07:26:09Zmrkn (Kenta Murata)muraken@gmail.com
<ul><li><strong>Description</strong> updated (<a title="View differences" href="/journals/61962/diff?detail_id=43335">diff</a>)</li><li><strong>Backport</strong> changed from <i>1.9.3: UNKNOWN, 2.0.0: UNKNOWN</i> to <i>2.0.0: UNKNOWN, 2.1: UNKNOWN, 2.2: UNKNOWN, 2.3: UNKNOWN</i></li></ul> Ruby master - Bug #8826: BigDecimal#div and #quo different behavior and inconsistencieshttps://bugs.ruby-lang.org/issues/8826?journal_id=621052016-12-20T03:26:59Zmrkn (Kenta Murata)muraken@gmail.com
<ul></ul><p>Sorry for the late response.<br>
I will fix this bug in the version of bigdecimal after releasing 1.3.</p> Ruby master - Bug #8826: BigDecimal#div and #quo different behavior and inconsistencieshttps://bugs.ruby-lang.org/issues/8826?journal_id=721892018-05-20T18:55:22Zkaratedog (Földes László)foldes.laszlo2@gmail.com
<ul></ul><p>How should #div work? The above behavior is still in Ruby 2.5.1.</p> Ruby master - Bug #8826: BigDecimal#div and #quo different behavior and inconsistencieshttps://bugs.ruby-lang.org/issues/8826?journal_id=875322020-09-11T18:39:46Zjeremyevans0 (Jeremy Evans)merch-redmine@jeremyevans.net
<ul><li><strong>Related to</strong> <i><a class="issue tracker-1 status-8 priority-4 priority-default closed" href="/issues/13754">Bug #13754</a>: bigdecimal with lower precision that Float</i> added</li></ul> Ruby master - Bug #8826: BigDecimal#div and #quo different behavior and inconsistencieshttps://bugs.ruby-lang.org/issues/8826?journal_id=950692021-12-03T01:46:41Zmrkn (Kenta Murata)muraken@gmail.com
<ul><li><strong>Status</strong> changed from <i>Assigned</i> to <i>Third Party's Issue</i></li></ul><p>The behavior of <code>BigDecimal#div</code> to return an Integer isn't a bug but the specification of <code>Numeric#div</code>. <code>Float#div</code> also always returns an Integer.</p>
<p>It is a bug that <code>BigDecimal#div</code> doesn't accept a Float without precision. I'll fix it in <a href="https://github.com/ruby/bigdecimal/issues/212" class="external">https://github.com/ruby/bigdecimal/issues/212</a>.</p>
<p><code>BigDecimal#quo</code> should be different from <code>BigDecimal#div</code> as <code>Numeric#quo</code> is different from <code>Numeric#div</code>. As <code>Float#quo</code> returns a Float, it is natural that <code>BigDecimal#quo</code> returns a BigDecimal.</p>
<p><code>BigDecimal#quo</code> must accept a precision of the result like <code>BigDecimal#div</code>. I'll fix it in <a href="https://github.com/ruby/bigdecimal/issues/214" class="external">https://github.com/ruby/bigdecimal/issues/214</a>.</p>