[#18121] [Ruby 1.8.7 - Bug #405] (Open) ssl.rb:31: [BUG] Bus Error — Anonymous <redmine@...>

Issue #405 has been reported by Anonymous.

14 messages 2008/08/04

[#18130] Re: New array methods cycle, choice, shuffle (plus bug in cycle) — Brian Candler <B.Candler@...>

> Seriously though... Array.first is a noun.

10 messages 2008/08/05

[#18319] NEW Command: absolute_path() -- — "C.E. Thornton" <admin@...>

Core,

14 messages 2008/08/16
[#18321] Re: NEW Command: absolute_path() -- — Yukihiro Matsumoto <matz@...> 2008/08/18

Hi,

[#18381] [Bug #496] DRb.start_service(nil) is very slow — Hongli Lai <redmine@...>

Bug #496: DRb.start_service(nil) is very slow

11 messages 2008/08/25

[ruby-core:18392] Re: [Feature #474] Hash#<<

From: Yukihiro Matsumoto <matz@...>
Date: 2008-08-27 05:04:03 UTC
List: ruby-core #18392
Hi,

In message "Re: [ruby-core:18370] [Feature #474] Hash#<<"
    on Sat, 23 Aug 2008 05:35:06 +0900, Anonymous <redmine@ruby-lang.org> writes:

|To recap, the idea is:
|
|  h = Hash.new
|  h << [:a, 1]
|  h << [:b, 2]
|  h #=> {:a=>1, :b=>2}
|
|This creates a polymorphism between associative arrays and hashes, which ultimately could be useful to mixins. And now that Hash supports insertion order too, it makes further sense. There was a particular usecase exemplified in the fore-mentioned thread. But since I can't find it I can't show it here. I just recall thinking it was compelling. Perhaps other's can recall?

Unlike Smalltalk's Dictionaries, Hashes in Ruby does not provide the
illusion of being sequence of association.  So the proposed new method
makes less sense in Ruby.

Besides that, Associative Arrays (which has normal array methods) and
hashes cannot behave polymorphic.

							matz.

In This Thread