From: Todd Benson <caduceass@...>
Date: 2007-06-22T05:06:54+09:00
Subject: Re: Behaviour of Enumerables reject vs. select mixed into Hash

On 6/21/07, Trans <transfire@gmail.com> wrote:
>
>
> > On 6/21/07, Rob Biedenharn <R...@agileconsultingllc.com> wrote:
> >
> > > What no one seems to have (directly) focussed on is that Hash#each
> > > gives two-element [k,v] arrays back as the content.
>
> That's right. And if you wanted things to be "just ducky", it would
> have to give only the v. I've actually argued in favor of that before,
> b/c it's not unreasonable to see that an Array index is like a Hash
> key.

Regardless of what we think is the best, it's seems pretty clear to me
that the duplicate of the Hash is broken during a delete_if, reject,
select, etc.  Thus, the array, and thus my comment about the array
being the LCD.  Like I said, I haven't read the Ruby source, but I'm
starting to get curious enough to do so.