From: Robert Dober <robert.dober@...>
Date: 2007-06-23T00:28:56+09:00
Subject: Re: Behaviour of Enumerables reject vs. select mixed into Hash

On 6/22/07, Todd Benson <caduceass@gmail.com> wrote:
> On 6/22/07, Robert Dober <robert.dober@gmail.com> wrote:
> > BTW all this does not answer OP's, Tom's and my *original* concern.
> > We were talking about Hash#reject and Hash#select not
> > Enumerable#reject and Enumerable#select, but nobody seems to notice,
> > sigh :(
> > This topic would be less difficult to discuss I think.
>
> My hash isn't your hash.  What's the most generic behavior to expect?
>
> See, you've already dismissed me right there, because you've decided
> if my Hash doesn't work the way _you_ expect it to, it's my fault.
I do not recall having dismissed you at all? I have mad a judgement
about two levels of complexity. If you do not like the behavior of
Hash#reject or Hash#select it might be a good idea to say so, right?
I do not mind at all if somebody says, I like Hash#reject to return a
Set because (this is just an example) etc. etc.

I guess I got confused about who thinks what in this thread :(
>
> >
> > Offense, are you kidding? The only thing which bothers me from a set
> > theory point of view is the symmetry in your statement above.
> >
> > Honestly Todd if you wanted to make a point I missed it, completely...
>
> That wouldn't be the first time I've been accused of saying a whole
> lot of nothin' :)
>
> I stopped talking about Ruby, and started talking instead about
> programming in general.  I introduced too many things at once.  My
> bad.
Indead ;)
>
> Todd
>
>


-- 
You see things; and you say Why?
But I dream things that never were; and I say Why not?
-- George Bernard Shaw