Eric Hodel wrote: > =begin > ... Good point. This feature would violate the invariant of hash keys being unique. You may reject this feature request. Thanks.sunaku (Suraj Kurapati)
Hi, ko1 (Koichi Sasada) wrote: > > ... Ah, I finally understand now. Thank you for explaining! :-) > I agree to add another interface to tell the stack range. But > ... Very well; that is reasonable. I agree with your decisio...sunaku (Suraj Kurapati)
ko1 (Koichi Sasada) wrote: > > 1. Cannot bind Ruby to a pre-allocated stack address range. > ... Changeset r38905 did not include my ruby_bind_stack() function. Without that function (or something similar), I cannot tell Ruby 2.0.0...sunaku (Suraj Kurapati)
Hello ko1, Thanks for committing changeset r38905 into Ruby 2.0.0-rc2. But, I am seeing the following problems with that changeset: 1. Cannot bind Ruby to a pre-allocated stack address range. 2. In my coroutine example, onl...sunaku (Suraj Kurapati)
Hi Matz, matz (Yukihiro Matsumoto) wrote: > The reason I hesitate to add to_h to nil is because I am not fully satisfied with nil.to_a etc. > ... Thank you very much for accepting nil.to_h in issue #6276. ^_^ I just read about th...sunaku (Suraj Kurapati)
Thanks for your agreement Thomas. Hey Ruby-core developers, we have agreed on the following API, where passing a File::FNM_EXTGLOB flag (the name "extglob" comes from the Bash/Zsh option for extended globbing) to the File.fnmatch meth...sunaku (Suraj Kurapati)
Hello, I am using ruby 1.9.3p194 (2012-04-20 revision 35410) [x86_64-linux]. There is no way to deactivate a Hash's compare by identity behavior: h = Hash.new h.compare_by_identity h.compare_by_identity? #=> true h.co...sunaku (Suraj Kurapati)
Hello, This patch still works as-is with ruby-1.9.3-p194 and ruby-1.9.2-p320: https://github.com/sunaku/ruby/compare/trunk...2294_bind_stack.patch My coroutine example still needs this patch to succeed under Ruby 1.9: https:/...sunaku (Suraj Kurapati)
In my mind, nil.to_h should exist for the same reason that nil.to_a, nil.to_s, nil.to_i, and nil.to_f exist: convenience. It allows me to write: some_complicated_method.to_h.each { ... } Instead of being forced to write: ...sunaku (Suraj Kurapati)
Hi Matz, I didn't ask for antonmys for all predicates; only for #exclude?. The reason for #exclude? is for more "natural" boolean expressions: if File.exist? some_file and some_list.exclude? some_file if File.exist? som...sunaku (Suraj Kurapati)