From: Matthew Kerwin <matthew@kerwin.net.au>
To: Ruby developers <ruby-core@ruby-lang.org>
Subject: [ruby-core:71499] Re: [Ruby trunk - Feature #11690] [Open] Update Hash during multiple assignment
Date: Mon, 16 Nov 2015 07:04:52 +1000 [thread overview]
Message-ID: <CACweHNBs7VXuhMPVSYsv8J1xNxA2vrchRT0JEDcLUX9yJ3++Bg@mail.gmail.com> (raw)
In-Reply-To: <redmine.issue-11690.20151115163053.5a303dbd5be813a1@ruby-lang.org>
[-- Attachment #1: Type: text/plain, Size: 1026 bytes --]
On 16/11/2015 2:32 AM, <6ftdan@gmail.com> wrote:
>
> This would be most useful in scenarios where a method or proc return
multiple values. When the method returns the values we don't normally know
the key outside where the hash assignment is.
>
> ~~~ruby
> example = proc { [{:hi => :hello}, 5] }
>
> hash = {}
>
> # Currently in Ruby with an Unknown key multiple assignment isn't an
option
> hash[????], current = example.call
>
> # We currently have to two step it
> result, current = example.call
> hash.update(result)
> ~~~
>
> But with `Hash#update=` we don't have to know the key.
>
I get the use-case, but I think the understandability of the code starts to
suffer.
What about something completely new but splat-like?
hash[*], current = example.call
This is even better when the hash comes last, it looks more like an options
parameter:
opts = get_default_hash
a, b, opts[*] = example2.call
I would assume this also works in single assignment:
opts = get_default_hash
opts[*] = get_new_opts
[-- Attachment #2: Type: text/html, Size: 1398 bytes --]
next prev parent reply other threads:[~2015-11-15 20:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <redmine.issue-11690.20151115163053@ruby-lang.org>
2015-11-15 16:30 ` [ruby-core:71495] [Ruby trunk - Feature #11690] [Open] Update Hash during multiple assignment 6ftdan
2015-11-15 21:04 ` Matthew Kerwin [this message]
2015-11-16 14:17 ` [ruby-core:71507] [Ruby trunk - Feature #11690] " 6ftdan
2015-11-16 21:31 ` [ruby-core:71508] " Matthew Kerwin
2015-11-17 1:29 ` [ruby-core:71509] " nobu
2015-11-17 2:10 ` [ruby-core:71510] " 6ftdan
2015-11-17 3:06 ` [ruby-core:71514] " nobu
2015-11-17 11:41 ` [ruby-core:71519] " 6ftdan
2015-11-18 18:41 ` [ruby-core:71562] " 6ftdan
2015-11-18 19:13 ` [ruby-core:71563] " 6ftdan
2015-11-22 23:29 ` [ruby-core:71635] " 6ftdan
2015-12-10 12:26 ` [ruby-core:72030] " 6ftdan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.ruby-lang.org/en/community/mailing-lists/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CACweHNBs7VXuhMPVSYsv8J1xNxA2vrchRT0JEDcLUX9yJ3++Bg@mail.gmail.com \
--to=ruby-core@ruby-lang.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).