On Wed, Nov 7, 2012 at 10:34 AM, Jermaine O. <[email protected]> wrote:
> Jan E. wrote in post #1083271: > > Well, in this case I don't really see the advantage of using sets. The > > only difference it makes is that arr_1 | arr_2 becomes > > set_1.merge(set_2). > > > > So unless you plan to actually use the special features of sets, I'd > > stick with standard arrays. > > > > But I don't want this to turn into yet another endless discussion about > > implementation details, so do whatever you think fits best. > Yeah. I just tend to use Set in situations where the content is supposed to be unique - if not for efficiency reasons then for documentation. > Got the work done and stuck with the merge block approach. Sorry, what did you mean? Are you still stuck or were you stuck? Kind regards robert -- remember.guy do |as, often| as.you_can - without end http://blog.rubybestpractices.com/ -- You received this message because you are subscribed to the Google Groups ruby-talk-google group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at https://groups.google.com/d/forum/ruby-talk-google?hl=en
