From: "nathan.f77 (Nathan Broadbent)" <nathan.f77@...>
Date: 2012-11-07T10:06:00+09:00
Subject: [ruby-core:49008] [ruby-trunk - Feature #7292] Enumerable#to_h


Issue #7292 has been updated by nathan.f77 (Nathan Broadbent).


> So what's the difference from rejected #7241?

The main difference is that `to_h` wouldn't take a block or any arguments. It would be a simple conversion from Enumerable to Hash, and would only support a collection of arrays containing a maximum of 2 elements.
----------------------------------------
Feature #7292: Enumerable#to_h
https://bugs.ruby-lang.org/issues/7292#change-32525

Author: marcandre (Marc-Andre Lafortune)
Status: Feedback
Priority: Low
Assignee: 
Category: core
Target version: 


Now that #to_h is the official method for explicit conversion to Hash, we should also add

	Enumerable#to_h: Returns a hash for the yielded key-value pairs.

	  [[:name, 'Joe Smith'], [:age, 42]].to_h # => {name: 'Joe Smith', age: 42}


With the Ruby tradition of succint documentation I suggest the documentation talk about key-value pairs and there is no need to be explicit about the uninteresting cases like:

    (1..3).to_h           # => {1 => nil, 2 => nil, 3 => nil}
    [[1, 2], [1, 3]].to_h # => {1 => 3}
    [[1, 2], []].to_h     # => {1 => 2, nil => nil}

I see some reactions of people reading about the upcoming 2.0 release like this one:
http://globaldev.co.uk/2012/11/ruby-2-0-0-preview-features/#dsq-comment-body-700242476



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