From: "marcandre (Marc-Andre Lafortune)" <ruby-core@...>
Date: 2012-03-29T11:11:06+09:00
Subject: [ruby-core:43835] [ruby-trunk - Bug #6203] Array#values_at does not handle ranges with end index past the end of the array


Issue #6203 has been updated by marcandre (Marc-Andre Lafortune).


Hi,

naruse (Yui NARUSE) wrote:
> Is this a bug?

I'm very curious: how could it not be bug?
How would you explain that `values_at(2...42) != values_at(2..41)`?

I simply want to lighten the load for Matz; he has so many issues assigned to him or waiting on him already.
----------------------------------------
Bug #6203: Array#values_at does not handle ranges with end index past the end of the array
https://bugs.ruby-lang.org/issues/6203#change-25345

Author: ferrous26 (Mark Rada)
Status: Assigned
Priority: Normal
Assignee: matz (Yukihiro Matsumoto)
Category: core
Target version: 2.0.0
ruby -v: trunk


=begin
When I use Array#values_at I expect that it would be the same as successive calls to (({Array#[]})).

There is one case where this does not hold:

    a = [0,1,2,3,4,5]
    a[4..6] # => [4, 5]
    a.values_at(4..6) # => [4,5,nil]

I think this is an inconsistency in the design of (({Array#values_at})). We can look at a more extreme case:

    a[4..100] # => [4, 5]
    a.values_at 4..100 # => [4, 5, nil]

And now it doesn't make any sense.

I think the best solution would be to make (({Array#values_at})) be equivalent to successive calls to (({Array#[]})). I have patched (({rb_range_beg_len()})) to handle the extra case and opened a pull request on github.
=end


-- 
http://bugs.ruby-lang.org/