[#18121] [Ruby 1.8.7 - Bug #405] (Open) ssl.rb:31: [BUG] Bus Error — Anonymous <redmine@...>

Issue #405 has been reported by Anonymous.

14 messages 2008/08/04

[#18130] Re: New array methods cycle, choice, shuffle (plus bug in cycle) — Brian Candler <B.Candler@...>

> Seriously though... Array.first is a noun.

10 messages 2008/08/05

[#18319] NEW Command: absolute_path() -- — "C.E. Thornton" <admin@...>

Core,

14 messages 2008/08/16
[#18321] Re: NEW Command: absolute_path() -- — Yukihiro Matsumoto <matz@...> 2008/08/18

Hi,

[#18381] [Bug #496] DRb.start_service(nil) is very slow — Hongli Lai <redmine@...>

Bug #496: DRb.start_service(nil) is very slow

11 messages 2008/08/25

[ruby-core:18070] Re: New array methods cycle, choice, shuffle (plus bug in cycle)

From: Jim Weirich <jim.weirich@...>
Date: 2008-08-01 20:45:00 UTC
List: ruby-core #18070
On Aug 1, 2008, at 2:40 PM, Thomas Enebo wrote:

> Actually 'sample(n=1)' seems like it make a lot more sense than  
> 'choice' (if you assume that it is useful that Array has this method  
> in the first place).  sampling data is a pretty common phrase.

The problem I have with this is that sample returns an array of  
elements.  I have occasionally run into the need for a single random  
element of the array.  I have never run into the problem of needing  
multiple samples.  I think the multiple sample solution solves a  
problem even rarer that the original single problem of a single random  
element (and still doesn't supply a direct solution for that).[1]

Of course, I'm only talking about my own experience.  Take that with a  
grain of salt.

-- 
-- Jim Weirich
-- jim.weirich@gmail.com

[1] Yes, I know you can do arr.sample.first.  Blech.[2]

[2] And if anyone suggests that sample(1) should return a single  
element and sample(2) should return an array, I will ... Well, I don't  
know what I'll do.  But it won't be pretty.


In This Thread