From: Jason Merrill <jason.merrill@...>
Date: 2006-08-29T11:24:47+09:00
Subject: Re: Should Array.new(n, obj) be deprecated?

> it's OK for Ruby to have *some* learning
> curve, and to be optimized for people who are planning to spend some
> time with it.

I agree with this statement completely, and I think you're right that
many of the things new users complain about tend to be the way they
are because it makes life better for experienced users; however, in
this particular case, I don't think the form of the constructor that I
was complaining about is optimized for experienced users.  I'd be
interested to hear about any time someone wants to fill an array with
references to a single instance of a mutable object--I have a feeling
that there aren't many.

And to correct a minor typo, in my explanation of the common gotcha,
when I said

If I want to make an array of 5 hashes, ...

I should have said

If I want to make an array of 6 hashes, ...

in order to be consistent with the rest of the example.