[#60404] is RB_GC_GUARD needed in rb_io_syswrite? — Eric Wong <normalperson@...>
I haven't gotten it to crash as-is, but it seems like we need to
4 messages
2014/02/01
[#60682] volatile usages — Eric Wong <normalperson@...>
Hi all, I went ahead and removed some use of volatile which were once
5 messages
2014/02/13
[#60794] [RFC] rearrange+pack vtm and time_object structs — Eric Wong <normalperson@...>
Extracted from addendum on top of Feature #9362 (cache-aligned objects).
4 messages
2014/02/16
[#61139] [ruby-trunk - Feature #9577] [Open] [PATCH] benchmark/driver.rb: align columns in text output — normalperson@...
Issue #9577 has been reported by Eric Wong.
3 messages
2014/02/28
[ruby-core:60782] [ruby-trunk - Feature #9522] [Open] Float( "NaN" ), Float( "Infinity" )
From:
boris@...
Date:
2014-02-16 05:37:00 UTC
List:
ruby-core #60782
Issue #9522 has been reported by Boris Stitnicky.
----------------------------------------
Feature #9522: Float( "NaN" ), Float( "Infinity" )
https://bugs.ruby-lang.org/issues/9522
* Author: Boris Stitnicky
* Status: Open
* Priority: Normal
* Assignee:
* Category:
* Target version:
----------------------------------------
I have noticed that 0.0 / 0.0 returns NaN, but Float( "#{0.0 / 0.0}" ),
or simply Float( "NaN" ) does not return Float::NAN, failing instead.
To me, even inclusion of NaN among floats is somewhat questionable, but
since it's there, Float( "NaN" ) needs to be discussed. Same would go
for Float( "Infinity" ).
The issue here might be that not all the users are aware that NaN and
Infinity have special meaning in the context of floats, and they might
use these strings inadvertantly without actually meaning a Float.
--
http://bugs.ruby-lang.org/