[#80974] [Ruby trunk Feature#13517] [PATCH] reduce rb_mutex_t size from 160 to 80 bytes on 64-bit — ko1@...
Issue #13517 has been updated by ko1 (Koichi Sasada).
4 messages
2017/05/02
[#81024] Re: [Ruby trunk Feature#13517] [PATCH] reduce rb_mutex_t size from 160 to 80 bytes on 64-bit
— SASADA Koichi <ko1@...>
2017/05/07
sorry for late response.
[#80996] [Ruby trunk Feature#13544] Allow loading an ISeqs sequence directly from a C extension without requiring buffer is in an RVALUE — sam.saffron@...
Issue #13544 has been reported by sam.saffron (Sam Saffron).
3 messages
2017/05/04
[#81016] [Ruby trunk Bug#13526] Segmentation fault at 0x0055c2e58e8920 ruby 2.3.1p112 (2016-04-26 revision 54768) [x86_64-linux] — s.wanabe@...
Issue #13526 has been updated by wanabe (_ wanabe).
3 messages
2017/05/07
[#81048] Re: [ruby-cvs:65788] normal:r58614 (trunk): rb_execution_context_t: move stack, stack_size and cfp from rb_thread_t — SASADA Koichi <ko1@...>
It causes compile error on raspi 3.
3 messages
2017/05/09
[#81201] Re: [ruby-cvs:65935] normal:r58761 (trunk): test/test_extilibs.rb: do not check the existence of fiddle — "U.NAKAMURA" <usa@...>
Hi, Eric
4 messages
2017/05/16
[#81202] Re: [ruby-cvs:65935] normal:r58761 (trunk): test/test_extilibs.rb: do not check the existence of fiddle
— Eric Wong <normalperson@...>
2017/05/16
"U.NAKAMURA" <[email protected]> wrote:
[#81427] Fwd: [ruby-changes:46809] normal:r58924 (trunk): test for IO.copy_stream CPU usage (r58534) — SASADA Koichi <ko1@...>
Hi,
6 messages
2017/05/28
[#81428] Re: Fwd: [ruby-changes:46809] normal:r58924 (trunk): test for IO.copy_stream CPU usage (r58534)
— Eric Wong <normalperson@...>
2017/05/28
SASADA Koichi <[email protected]> wrote:
[ruby-core:81012] [Ruby trunk Bug#13420] Integer#{round, floor, ceil, truncate} should always return an integer, not a float
From:
eregontp@...
Date:
2017-05-06 20:38:25 UTC
List:
ruby-core #81012
Issue #13420 has been updated by Eregon (Benoit Daloze).
stomar (Marcus Stollsteimer) wrote:
> Applied.
> I opened a PR for the specs: https://github.com/ruby/spec/pull/436
Thanks!
> Should I add a comment in `NEWS` or not?
Yes, I think the rule is to add a NEWS entry for every user-visible behavior change.
----------------------------------------
Bug #13420: Integer#{round,floor,ceil,truncate} should always return an integer, not a float
https://bugs.ruby-lang.org/issues/13420#change-64676
* Author: stomar (Marcus Stollsteimer)
* Status: Closed
* Priority: Normal
* Assignee: stomar (Marcus Stollsteimer)
* Target version:
* ruby -v: r58307
* Backport: 2.2: UNKNOWN, 2.3: UNKNOWN, 2.4: UNKNOWN
----------------------------------------
The current behavior of Integer#{round,floor,ceil,truncate} produces wrong results for large integers.
In the case of a positive precision argument, these methods return the receiver converted to a float, effectively doing the same as `to_f`.
```
2.round(1) # => 2.0
```
This leads to errors for large integers:
```
(10**25).round(2).to_i # => 10000000000000000905969664
(10**400).round(2) # => Infinity
```
Mathematically speaking, the value of an integer should not be changed by #round, #floor, #ceil, or #truncate, regardless of the precision (when positive). An integer rounded to e.g. 2 decimal digits is still the same (and exact) integer.
The desired behavior should be to keep precision as high as possible by not needlessly converting to Float.
The provided patch fixes these methods to return `self` for positive precision argument, similar to the behavior without a specified precision, i.e. precision 0.
---Files--------------------------------
0001-Integer-round-floor-ceil-truncate.patch (7.83 KB)
--
https://bugs.ruby-lang.org/
Unsubscribe: <mailto:[email protected]?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>