[#64703] Add `Hash#fetch_at` (issue #10017) — Wojtek Mach <wojtek@...>
Hey guys
1 message
2014/09/01
[#64711] [ruby-trunk - Bug #10193] [Closed] TestIO#test_readpartial_locktmp fails randomly — nobu@...
Issue #10193 has been updated by Nobuyoshi Nakada.
3 messages
2014/09/02
[#64744] [ruby-trunk - Bug #10202] [Open] TestBenchmark#test_realtime_output breaks on ARM — v.ondruch@...
Issue #10202 has been reported by Vit Ondruch.
3 messages
2014/09/03
[#64823] documenting constants — Xavier Noria <fxn@...>
I am writing a Rails guide about constant autoloading in Ruby on
5 messages
2014/09/07
[#64838] [ruby-trunk - Bug #10212] [Open] MRI is not for lambda calculus — ko1@...
Issue #10212 has been reported by Koichi Sasada.
6 messages
2014/09/08
[#64858] Re: [ruby-trunk - Bug #10212] [Open] MRI is not for lambda calculus
— Eric Wong <normalperson@...>
2014/09/08
rb_env_t may use a flexible array, helps a little even on my busy system:
[#64871] Re: [ruby-trunk - Bug #10212] [Open] MRI is not for lambda calculus
— SASADA Koichi <ko1@...>
2014/09/08
(2014/09/08 19:48), Eric Wong wrote:
[#64972] [ruby-trunk - Bug #10231] [Open] Process.detach(pid) defines new singleton classes every call — headius@...
Issue #10231 has been reported by Charles Nutter.
3 messages
2014/09/11
[#64980] [ruby-trunk - Bug #10212] MRI is not for lambda calculus — ko1@...
Issue #10212 has been updated by Koichi Sasada.
4 messages
2014/09/12
[#65142] [ruby-trunk - Feature #10267] [Open] Number of processors — akr@...
Issue #10267 has been reported by Akira Tanaka.
4 messages
2014/09/20
[#65144] Re: [ruby-trunk - Feature #10267] [Open] Number of processors
— Eric Wong <normalperson@...>
2014/09/20
akr@fsij.org wrote:
[#65210] [ruby-trunk - misc #10278] [Assigned] [RFC] st.c: use ccan linked list — nobu@...
Issue #10278 has been updated by Nobuyoshi Nakada.
3 messages
2014/09/22
[ruby-core:65193] [ruby-trunk - Feature #10270] Hash#insert
From:
a7145@...
Date:
2014-09-21 13:01:44 UTC
List:
ruby-core #65193
Issue #10270 has been updated by Atlas Prime.
The name "insert" seems good to me because it implies a *new* entry and unable to change an *old* entry. But key-value pair must be thought of as an *entry* too for it to make sense (I guess I get that notion from Java http://docs.oracle.com/javase/7/docs/api/java/util/Map.Entry.html).
I did not know that merge took this block. That could be useful. But it's not quite the same because insert returns true/false if successful of not. It's utility is mostly as a short cut for
if !h.key?(k)
store(k,v)
...
end
Instead one can do
if h.insert(k,v)
...
end
However, you make me think it might be useful too if it could take a hash and a block.
def insert_merge(other, &block)
other.each do |k, v|
if key?(k)
block.call(false, k, v)
else
store(k,v)
block.call(true, k, v)
end
end
end
----------------------------------------
Feature #10270: Hash#insert
https://bugs.ruby-lang.org/issues/10270#change-49031
* Author: Atlas Prime
* Status: Feedback
* Priority: Normal
* Assignee:
* Category: core
* Target version:
----------------------------------------
Hash doesn't appear to have a "safe" way to insert an entry that won't clobber another key if it is already there. So how about:
~~~
class Hash
# Like Hash#store but only stores if the key isn't already
# in the hash. Returns true if inserted, otherwise false.
#
def insert(name, value)
if key?(name)
false
else
store(name,value)
true
end
end
end
~~~
--
https://bugs.ruby-lang.org/