Hi,

From: "Michael Campbell" <michael_s_campbell / yahoo.com>
>
> > Anyone know why Array#uniq returns an array in every case and 
> > Array#uniq! returns nil if nothing is removed?  [...]
> 
> There are a number of "bang" methods that do this.  If I recall
> correctly, matz has said they do this so that you CAN'T chain the
> methods.

I thought Matz had said it was because there'd be no equally
efficient way to determine the did-anything-change test, otherwise.

I.e. so it's there, as a feature, because if you did need it
for efficiency's sake, there'd be no other way to do it.


?


Regards,

Bill