[#61171] Re: [ruby-changes:33145] normal:r45224 (trunk): gc.c: fix build for testing w/o RGenGC — SASADA Koichi <ko1@...>
(2014/03/01 16:15), normal wrote:
[#61243] [ruby-trunk - Feature #9425] [PATCH] st: use power-of-two sizes to avoid slow modulo ops — normalperson@...
Issue #9425 has been updated by Eric Wong.
[#61359] [ruby-trunk - Bug #9609] [Open] [PATCH] vm_eval.c: fix misplaced RB_GC_GUARDs — normalperson@...
Issue #9609 has been reported by Eric Wong.
(2014/03/07 19:09), normalperson@yhbt.net wrote:
SASADA Koichi <ko1@atdot.net> wrote:
[#61424] [REJECT?] xmalloc/xfree: reduce atomic ops w/ thread-locals — Eric Wong <normalperson@...>
I'm unsure about this. I _hate_ the extra branches this adds;
Hi Eric,
SASADA Koichi <ko1@atdot.net> wrote:
(2014/03/14 2:12), Eric Wong wrote:
SASADA Koichi <ko1@atdot.net> wrote:
[#61452] [ruby-trunk - Feature #9632] [Open] [PATCH 0/2] speedup IO#close with linked-list from ccan — normalperson@...
Issue #9632 has been reported by Eric Wong.
[#61496] [ruby-trunk - Feature #9638] [Open] [PATCH] limit IDs to 32-bits on 64-bit systems — normalperson@...
Issue #9638 has been reported by Eric Wong.
[#61568] hash function for global method cache — Eric Wong <normalperson@...>
I came upon this because I noticed existing st numtable worked poorly
(2014/03/18 8:03), Eric Wong wrote:
SASADA Koichi <ko1@atdot.net> wrote:
what's the profit from using binary tree in place of hash?
Юрий Соколов <funny.falcon@gmail.com> wrote:
[#61687] [ruby-trunk - Bug #9606] Ocassional SIGSEGV inTestException#test_machine_stackoverflow on OpenBSD — normalperson@...
Issue #9606 has been updated by Eric Wong.
[#61760] [ruby-trunk - Feature #9632] [PATCH 0/2] speedup IO#close with linked-list from ccan — normalperson@...
Issue #9632 has been updated by Eric Wong.
[ruby-core:61538] [ruby-trunk - Bug #9521] [Doc] Fix error in Time.parse documentation (in lib/time)
Issue #9521 has been updated by Marcus Stollsteimer.
@zak Just to consider: I used EST because
* the docs for `Time` state: _All of these examples were done using the EST timezone which is GMT-5._
* AFAIK it's not easily possible to set JST on the local machine (via environment variable) so that these examples can be reproduced, since it's not part of RFC 822. Setting to EST works fine (even in Germany):
2.1.1 :012 > ENV["TZ"] = "EST"
2.1.1 :013 > Time.parse("2014-01-01")
=> 2014-01-01 00:00:00 -0500
2.1.1 :014 > ENV["TZ"] = "JST"
2.1.1 :015 > Time.parse("2014-01-01")
=> 2014-01-01 00:00:00 +0000
----------------------------------------
Bug #9521: [Doc] Fix error in Time.parse documentation (in lib/time)
https://bugs.ruby-lang.org/issues/9521#change-45824
* Author: Marcus Stollsteimer
* Status: Closed
* Priority: Normal
* Assignee: Zachary Scott
* Category: doc
* Target version:
* ruby -v: ruby 2.1.0p0 (2013-12-25 revision 44422) [i686-linux]
* Backport: 1.9.3: UNKNOWN, 2.0.0: UNKNOWN, 2.1: UNKNOWN
----------------------------------------
The docs state that the examples are for GMT as local time zone while in fact they are for JST.
The patch fixes this by using EST (and saying so), like the rest of the examples for lib/time.
---Files--------------------------------
doc_lib_time.patch (1.13 KB)
--
http://bugs.ruby-lang.org/