[#70252] Re: [ruby-cvs:58640] nobu:r51492 (trunk): node.c: NODE_ALLOCA for ALLOCV — Eric Wong <normalperson@...>
Besides possible backwards compatibility, can we drop volatile
3 messages
2015/08/05
[#70257] [Ruby trunk - Feature #11420] [Open] Introduce ID key table into MRI — ko1@...
Issue #11420 has been reported by Koichi Sasada.
11 messages
2015/08/06
[#70337] Re: [Ruby trunk - Feature #11420] [Open] Introduce ID key table into MRI
— Eric Wong <normalperson@...>
2015/08/11
Nice. Thank you guys for looking into this.
[#70349] Re: [Ruby trunk - Feature #11420] [Open] Introduce ID key table into MRI
— Eric Wong <normalperson@...>
2015/08/12
Btw, did you consider using flexible array to avoid extra malloc
[#70355] Re: [Ruby trunk - Feature #11420] [Open] Introduce ID key table into MRI
— Юрий Соколов <funny.falcon@...>
2015/08/12
I thought to suggest to embed hash_id_table directly into places when it is
[#70356] Re: [Ruby trunk - Feature #11420] [Open] Introduce ID key table into MRI
— SASADA Koichi <ko1@...>
2015/08/12
On 2015/08/13 4:29, Юрий Соколов wrote:
[#70358] Re: [Ruby trunk - Feature #11420] [Open] Introduce ID key table into MRI
— Eric Wong <normalperson@...>
2015/08/12
SASADA Koichi <ko1@atdot.net> wrote:
[#70509] [Ruby trunk - Misc #11276] [RFC] compile.c: convert to use ccan/list — ko1@...
Issue #11276 has been updated by Koichi Sasada.
3 messages
2015/08/21
[#70639] the undefined behavior of an iterator if it is modified inside of the block to which it yields — Daniel Doubrovkine <dblock@...>
(this is my first time e-mailing list list, so apologies for any misstep :)
4 messages
2015/08/31
[ruby-core:70248] [Ruby trunk - Bug #11417] [Open] Wrong description for `limit` parameter for IO#gets
From:
ary@...
Date:
2015-08-05 09:48:52 UTC
List:
ruby-core #70248
Issue #11417 has been reported by Ary Borenszweig. ---------------------------------------- Bug #11417: Wrong description for `limit` parameter for IO#gets https://bugs.ruby-lang.org/issues/11417 * Author: Ary Borenszweig * Status: Open * Priority: Normal * Assignee: * ruby -v: * Backport: 2.0.0: UNKNOWN, 2.1: UNKNOWN, 2.2: UNKNOWN ---------------------------------------- It says: "If the first argument is an integer, or optional second argument is given, the returning string would not be longer than the given value in bytes." But: ~~~ require "stringio" io = StringIO.new "こんにちは" string = io.gets(1) puts string #=> "こ" puts string.bytes.length #=> 3 ~~~ The returning value number of bytes (3) is longer than the given value (1), so it contradicts the description. I guess the implementation reads chars until the total number of bytes read is equal or bigger than the limit. But I don't know how to describe this behaviour in a way that's clear to the user. -- https://bugs.ruby-lang.org/