[#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:70543] [Ruby trunk - Feature #11252] Integrated "did_you_mean" gem to ruby-core
From:
mail@...
Date:
2015-08-22 07:04:21 UTC
List:
ruby-core #70543
Issue #11252 has been updated by Yuki Nishijima.
We've discussed this at the Ruby developers meeting on Thursday and made several decisions(but still subject to change).
* We are not going to rename the gem (we'll just use `did_you_mean`)
* It'll be a bundled gem (Yuki will be responsible for releasing a version that works on Ruby 2.3 without C extensions)
* There should be a way of disabling this feature entirely (`--disable-gem did_you_mean` or `--disable-gemname`)
* There should be a method on `NameError` that returns a qualified name:
```ruby
class User; end
error = begin
User::DoesntExist
rescue NameError => e
e
end
error.name # => :Exist
error.qualified_name # => :"User::DoesntExist"
```
The last 2 features can be separate features. That said, since the last one is a blocker, it would be great if this could be done before actually having did_you_mean bundled.
----------------------------------------
Feature #11252: Integrated "did_you_mean" gem to ruby-core
https://bugs.ruby-lang.org/issues/11252#change-53951
* Author: Hiroshi SHIBATA
* Status: Open
* Priority: Normal
* Assignee: Hiroshi SHIBATA
----------------------------------------
Matz hope to integrate "did_you_mean" gem to Ruby 2.3
We need to solve to following issues.
* integrate [interception](https://github.com/ConradIrwin/interception/) gem
* naming(better name for did_you_mean)
* bundled policy(standard library? bundled gem?)
--
https://bugs.ruby-lang.org/