From: "marcandre (Marc-Andre Lafortune)" <ruby-core@...> Date: 2013-09-12T11:58:53+09:00 Subject: [ruby-core:57154] [ruby-trunk - Feature #8895] Destructuring Assignment for Hash Issue #8895 has been updated by marcandre (Marc-Andre Lafortune). chendo (Jack Chen) wrote: > No value variable after other_key: feels a bit off to me, too. Not surprising it feels off today, but you better get used to it because it's coming in 2.1.0: https://bugs.ruby-lang.org/issues/7701 ---------------------------------------- Feature #8895: Destructuring Assignment for Hash https://bugs.ruby-lang.org/issues/8895#change-41764 Author: chendo (Jack Chen) Status: Open Priority: Normal Assignee: Category: Target version: =begin Given Ruby already supports destructuring assignment with Array (a, b = [1, 2]), I propose destructuring assignments for Hash. == Basic example params = {name: "John Smith", age: 42} {name: name, age: age} = params # name == "John Smith" # age == 42 This would replace a common pattern of assigning hash values to local variables to work with. == General syntax { <key-expr> => <variable_name>, ��� } = <object that responds to #[]> # Symbols { foo: bar } = { foo: "bar" } bar == "bar" # Potential shorthand { foo } = { foo: "bar" } foo == "bar" == Use cases: # MatchData { username: username, age: age } = "user:jsmith age:42".match(/user:(?<username>\w+) age:(?<age>\d+)/) username == "jsmith" age == "42" == Edge cases # Variable being assigned to more than once should use the last one { foo: var, bar: var } = {foo: 1, bar: 2} var == 2 Thoughts? =end -- http://bugs.ruby-lang.org/