~~~ruby def foo(); :ok end foo(*[]) #=> :ok foo(**{}) #=> ArgumentError: wrong number of arguments (1 for 0) foo(*[], **{}) #=> ArgumentError: wrong number of arguments (1 for 0) ~~~ I was expecting kwargs splatting to work the s...zimbatm (zimba tm)
Alright but a change doesn't necessarily need to be substantial to improve developer happiness. It seems like my little hack has two aspects to it that I would like to address separately. `"foo".gsub("o")` currently doesn't do any sub...zimbatm (zimba tm)
Hi ruby devs ! A common case for string substitution is to just remove the found items. This patch changes the `String#[g]sub[!]` methods to allow that. Old usages: "foo".sub("o", "") #=> "fo" "foo".gsub("o", "") #=> "f...zimbatm (zimba tm)
=begin #pop is often associated to stack operations, which implies an order. Unless a better name is found, isn't set.delete(set.take) enough ? #take can be an alias of #first but I'm not sure if Enumerable should be included in Set i...zimbatm (zimba tm)
I don't see the advantage of having nil returned in any case since the empty array already expresses the "there is no object in that range". Out of bound can be tested separately if necessary, but most of the cases you just want to ge...zimbatm (zimba tm)
=begin Hi Marco, awesome lib. I read trough it and here are the thoughts I had: * IPAddr#[] and IPAddr#each don't hold the same elements, could it be a source of confusion ? * Is it possible to avoid extending the ruby core ? Cheers, J...zimbatm (zimba tm)
=begin Small documentation fixes for the syslog extension. The patch is a GIT patch on top of 7487298584145058f2340dc7a6e4da8d21fe5248. Please let me know if you need a SVN patch instead. Cheers, Jonas =end zimbatm (zimba tm)
=begin How is that a bug ? If ping is surrounded by quotes, ruby will look for an executable named "ping" with the quotes around. If ruby starts to magically remove these quotes, I'm not sure it will bring other unwanted side-effect. Bu...zimbatm (zimba tm)
=begin Actually, protecting from async exceptions in the ensure block would be mostly backward-compatible. It means that while a thread is in that part of the code, no other thread would be running. Only code that will break, would b...zimbatm (zimba tm)