From: Eyal Oren <eyal.oren@...>
Date: 2006-09-21T19:15:19+09:00
Subject: Re: Bug in Hash#hash? (Ruby 1.8.4)

Yukihiro Matsumoto wrote:
>> |say one = {:a=>:b}
>> |then one.hash != one.clone.hash
>> |is that a bug or correct?
> Currently it's an intended behavior.  Hash is not designed to be hash
> key (two hashes are considered to be a same key if they are exactly
> the same object).  It's not likely to change in 1.8 series.  In 1.9,
> maybe.
thanks for the clarification.
why was this decided?

is it not useful to have a hash as hash-key? I often use hashes to
emulate named parameter-values, and if I have say a connection pool I
would like to index it based on the connection-parameters (which are
given as a hash of key-value pairs). 

does this scenario make sense?