[#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:70550] [Ruby trunk - Feature #11477] NameError#qualified_name
From:
mail@...
Date:
2015-08-22 22:09:18 UTC
List:
ruby-core #70550
Issue #11477 has been updated by Yuki Nishijima. That actually makes more sense and is what we talked about at the last Ruby= developers meeting. According to Nobu it requires a lot of work, though. B= ut in terms of the interface, I'm =F0=9F=91=8D on `NameError#receiver` retu= rning the receiving module in a "uninitialized constant" NameError. ---------------------------------------- Feature #11477: NameError#qualified_name https://bugs.ruby-lang.org/issues/11477#change-53959 * Author: Yuki Nishijima * Status: Open * Priority: Normal * Assignee:=20 ---------------------------------------- Hi, This is a followup issue to #11252. I'd like to add a method that basically= does the same thing as [NameError#missing_name](https://github.com/rails/r= ails/blob/ebe73abea0ae02094ddc28f8fd60ae92373b6113/activesupport/lib/active= _support/core_ext/name_error.rb#L2-L14). This will allow gems like Rails an= d did_you_mean to get a qualified name without parsing an error message. ```ruby begin HelloWorld rescue NameError =3D> e error.name # =3D> :HelloWorld error.qualified_name # =3D> :HelloWorld end begin String::DoesntExist rescue NameError =3D> e error.name # =3D> :DoesntExist error.qualified_name # =3D> :"String::DoesntExist" end ``` I'm not actually sure what it should return when the module/class is an ano= nymous module/class, but one thing we can do is just use the result of `#to= _s`: ```ruby m =3D Module.new begin m::DoesntExist rescue NameError =3D> e error.name # =3D> :DoesntExist error.qualified_name # =3D> :"#<Module:0x0000000260c2f8>::DoesntExist" end ``` I'm open to suggestions. Let me know what you think. Yuki --=20 https://bugs.ruby-lang.org/