[ruby-core:74275] Re: [Ruby trunk Feature#12165] Hash#first, Hash#last

There's documentation for `#first`, you need to look for it in
`Enumerable`, rather than `Hash`:
http://docs.ruby-lang.org/en/2.3.0/Enumerable.html#method-i-first

Enumerable lacks a `#last` method. I presume the main reason for that is
because an enumerable object may not have a last element.

On 10 March 2016 at 19:00, <[e-mail]> wrote:

> Issue #12165 has been reported by Fabian Stillhart.
>
> ----------------------------------------
> Feature #12165:  Hash#first, Hash#last
> https://bugs.ruby-lang.org/issues/12165
>
> * Author: Fabian Stillhart
> * Status: Open
> * Priority: Normal
> * Assignee:
> ----------------------------------------
> Just run into a simple problem with a colleague and was wondering why
> there is no Hash#last method?
>
> ~~~ruby
> {a: true, b: false}.last
> NoMethodError: undefined method 'last' for {:a=>true, :b=>false}:Hash
> ~~~
>
> Interestingly I while playing arround I found out that the Hash#first
> method works. But why is it not in the ruby-doc?
>
> ~~~ruby
> {a: true, b: false}.first
> => [:a, true]
> ~~~
>
> I would assume the Hash#last method would work like the Hash#first method:
>
> ~~~ruby
> {a: true, b: false}.last
> => [:b, false]
> ~~~
>
> If I am not wrong the order of a Hash is always the same when calling
> Hash#each. So wouldn't it make sense to have Hash#last method?
>
> I tested it in Ruby 2.2.4 and Ruby 2.3.0.
>
>
>
> --
> https://bugs.ruby-lang.org/
>
> Unsubscribe: <mailto:[e-mail]?subject=unsubscribe>
> <http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>
>



-- 
Jes炭s Burgos Maci叩

Unsubscribe: <mailto:[e-mail]?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>