# Select!

**URL:** <https://www.ruby-forum.com/t/select/180247>\
**Category:** Ruby\
**Created:** [December 15, 2009, 7:35pm UTC](https://www.ruby-forum.com/t/select/180247 "2009-12-15T19:35:44Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![rogerdpack](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/r/45deac/32.png) [@rogerdpack](https://www.ruby-forum.com/u/rogerdpack)\
**Post date:** [December 15, 2009, 7:35pm UTC](https://www.ruby-forum.com/t/select/180247/1 "2009-12-15T19:35:44Z")

</div>

Is there any reason there’s no select!  
(and I am familiar with compact! but still…)

C:\>ruby -e ‘puts [].methods.grep /reject/’  
reject  
reject!

C:\>ruby -e ‘puts [].methods.grep /select/’  
select

---

<div class="post-metadata">

**Author:** ![rogerdpack](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/r/45deac/32.png) [@rogerdpack](https://www.ruby-forum.com/u/rogerdpack)\
**Post date:** [December 15, 2009, 9:58pm UTC](https://www.ruby-forum.com/t/select/180247/2 "2009-12-15T21:58:31Z")

</div>

On Dec 15, 2009, at 10:35 , Roger P. wrote:

> Is there any reason there’s no select!

Perhaps because `select! x` is as simple as `reject! not x`?

---

<div class="post-metadata">

**Author:** ![rogerdpack](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/r/45deac/32.png) [@rogerdpack](https://www.ruby-forum.com/u/rogerdpack)\
**Post date:** [December 16, 2009, 2:27am UTC](https://www.ruby-forum.com/t/select/180247/3 "2009-12-16T02:27:08Z")

</div>

On Tuesday 15 December 2009 02:51:56 pm Ryan D. wrote:

> On Dec 15, 2009, at 10:35 , Roger P. wrote:
> 
> > Is there any reason there’s no select!
> 
> Perhaps because `select! x` is as simple as `reject! not x`?

For consistency’s sake, I’d still suggest the standard library should  
provide  
something like:

module Enumerable  
def select!  
reject! {|\*args| ! yield(\*args) }  
end  
def reject!  
select! {|\*args| ! yield(\*args) }  
end  
end

Not exactly that, though – the obvious problem is that if neither  
select! no  
reject! is overridden, you’d want a NoMethodError instead of a stack  
overflow.

---

<div class="post-metadata">

**Author:** ![rogerdpack](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/r/45deac/32.png) [@rogerdpack](https://www.ruby-forum.com/u/rogerdpack)\
**Post date:** [December 22, 2009, 3:54pm UTC](https://www.ruby-forum.com/t/select/180247/4 "2009-12-22T15:54:25Z")

</div>

> For consistency’s sake, I’d still suggest the standard library should  
> provide  
> something like:
> 
> module Enumerable  
> def select!  
> reject! {|\*args| ! yield(\*args) }  
> end  
> def reject!  
> select! {|\*args| ! yield(\*args) }  
> end  
> end

Anybody in favor of select!  
Could comment on  
[http://redmine.ruby-lang.org/issues/show/2515](http://redmine.ruby-lang.org/issues/show/2515)

-r

---

<div class="post-metadata">

**Author:** ![rogerdpack](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/r/45deac/32.png) [@rogerdpack](https://www.ruby-forum.com/u/rogerdpack)\
**Post date:** [December 22, 2009, 4:13pm UTC](https://www.ruby-forum.com/t/select/180247/5 "2009-12-22T16:13:26Z")

</div>

On Tue, Dec 22, 2009 at 9:54 AM, Roger P. [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid)  
wrote:

> > ```
> > select! {|*args| ! yield(*args) }
> > 
> > ```
> > 
> > end  
> > end

-1

Enumerable does not have a reject! since not all Enumerables are  
mutable either in general or during enumeration.

Also the given suggestion would lead to infinite loops, unless reject!  
or select! was overridden in the including class.

–  
Rick DeNatale

Blog: [http://talklikeaduck.denhaven2.com/](http://talklikeaduck.denhaven2.com/)  
Twitter: [http://twitter.com/RickDeNatale](http://twitter.com/RickDeNatale)  
WWR: [NameBright - Coming Soon](http://www.workingwithrails.com/person/9021-rick-denatale)  
LinkedIn: [http://www.linkedin.com/in/rickdenatale](http://www.linkedin.com/in/rickdenatale)

---

<div class="post-metadata">

**Author:** ![rogerdpack](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/r/45deac/32.png) [@rogerdpack](https://www.ruby-forum.com/u/rogerdpack)\
**Post date:** [December 22, 2009, 5:03pm UTC](https://www.ruby-forum.com/t/select/180247/6 "2009-12-22T17:03:47Z")

</div>

2009/12/15 Roger P. [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid):

> Is there any reason there’s no select!  
> (and I am familiar with compact! but still…)
> 
> C:\>ruby -e ‘puts .methods.grep /reject/’  
> reject  
> reject!
> 
> C:\>ruby -e ‘puts .methods.grep /select/’  
> select

Maybe Matz felt that using “select” to actually _delete_ from an Array  
would be considered weird. And indeed, we have #delete, #delete\_at  
and #delete\_if:

irb(main):001:0\> Array.instance\_methods.grep /delete/  
=\> [:delete, :delete\_at, :delete\_if]  
irb(main):002:0\>

🙂

Kind regards

robert

---

<div class="post-metadata">

**Author:** ![rogerdpack](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/r/45deac/32.png) [@rogerdpack](https://www.ruby-forum.com/u/rogerdpack)\
**Post date:** [December 22, 2009, 9:14pm UTC](https://www.ruby-forum.com/t/select/180247/7 "2009-12-22T21:14:18Z")

</div>

On 22.12.2009 17:29, Roger P. wrote:

> His words:
> 
> > Enumerables cannot have bang method, since they are not always  
> > mutable. The reason we don’t have Array#select! is that I feel the  
> > word select means picking up elements, not removing non-selecting  
> > elements. But I once felt same way to map! and (English speaking)  
> > people persuaded me, so same thing could happen on select! as well.
> 
> So yes but hopefully I can change his mind 🙂

The second “SELECT \* FROM TABLE” deletes the records I want to retrieve  
from a DBMS, I agree with you. 😉

---

<div class="post-metadata">

**Author:** ![rogerdpack](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/r/45deac/32.png) [@rogerdpack](https://www.ruby-forum.com/u/rogerdpack)\
**Post date:** [December 22, 2009, 5:28pm UTC](https://www.ruby-forum.com/t/select/180247/8 "2009-12-22T17:28:53Z")

</div>

> Enumerable does not have a reject! since not all Enumerables are  
> mutable either in general or during enumeration

Yeah this is a feature request only for Array#select!

[Enumerable doesn’t have a reject! nor should it have a select!]

> Maybe Matz felt that using “select” to actually _delete_ from an Array  
> would be considered weird. And indeed, we have #delete, #delete\_at  
> and #delete\_if:

His words:

> Enumerables cannot have bang method, since they are not always  
> mutable. The reason we don’t have Array#select! is that I feel the  
> word select means picking up elements, not removing non-selecting  
> elements. But I once felt same way to map! and (English speaking)  
> people persuaded me, so same thing could happen on select! as well.

So yes but hopefully I can change his mind 🙂

-r
