From: matz@... (Yukihiro Matsumoto)
Date: 2002-01-26T19:49:36+09:00
Subject: Re: Serious Array Bug in Ruby 1.6.6?

Hi,

In message "Re: Serious Array Bug in Ruby 1.6.6?"
    on 02/01/26, William Djaja Tjokroaminata <billtj@y.glue.umd.edu> writes:

|Ruby has done a lot of checkings, like public/protected/private methods,
|and attr_reader/attr_accessor methods.  For Array, why not just check the
|type/class of obj when the array is created, just like what you do
|for singleton?  If a program has to create and destroy arrays many many
|times, probably it should have been written in C.

The point is what kind of check should be done.  Copying the fill
value (the second optional argument to Array::new) implicitly is
confusing for me.  One possible idea is

  Array::new(2) {Hash.new}

fills evaluated values from block.

							matz.