From: "zverok (Victor Shepelev)" <noreply@ruby-lang.org>
To: ruby-core@ruby-lang.org
Subject: [ruby-core:109873] [Ruby master Feature#19001] Data: Add #to_h symmetric to constructor with keyword args [Follow-on to #16122 Data: simple immutable value object]
Date: Sat, 10 Sep 2022 13:24:04 +0000 (UTC) [thread overview]
Message-ID: <redmine.journal-99113.20220910132403.1343@ruby-lang.org> (raw)
In-Reply-To: redmine.issue-19001.20220908183725.1343@ruby-lang.org
Issue #19001 has been updated by zverok (Victor Shepelev).
There isn't any need for this ticket as a separate request, as far as I am concerned.
It works in the initial implementation of data already as submitted in https://bugs.ruby-lang.org/issues/16122#note-68, and even works with ol' good Struct, too:
```ruby
Point = Struct.new(:x, :y, :z)
Point[1, 0, 0].to_h.then { Point[**_1] } == Point[1, 0, 0] # => true
```
----------------------------------------
Feature #19001: Data: Add #to_h symmetric to constructor with keyword args [Follow-on to #16122 Data: simple immutable value object]
https://bugs.ruby-lang.org/issues/19001#change-99113
* Author: RubyBugs (A Nonymous)
* Status: Open
* Priority: Normal
----------------------------------------
*Extracted a follow-up to [#16122 Data: simple immutable value object](https://bugs.ruby-lang.org/issues/16122)*
# Proposal: Add a `#to_h` method symmetric to a constructor accepting keyword arguments
This allows round-trip between a `Hash` and a Value object instance, for example:
```ruby
Point = Data.define(:x, :y, :z)
points = [
Point.new(x: 1, y: 0, z: 0),
Point.new(x: 0, y: 1, z: 0),
Point.new(x: 0, y: 0, z: 1),
]
hashes = points.map(&:to_h)
points_2 = hashes.map { |h| Point.new(**h) }
points_2 == points
#=> true
```
## Why?
Having symmetric operation between `#to_h` and a keyword-args constructor is a major ergonomic factor in usage of immutable value objects.
To play with code that works like this, you may take a look at the [Values gem](https://rubygems.org/gems/values)
## Alternatives
If there is no symmetric construction and de-construction along these lines, a number of use cases become more complicated and less ergonomic.
--
https://bugs.ruby-lang.org/
prev parent reply other threads:[~2022-09-10 13:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-08 18:37 [ruby-core:109853] [Ruby master Feature#19001] Data: Add #to_h symmetric to constructor with keyword args [Follow-on to #16122 Data: simple immutable value object] RubyBugs (A Nonymous)
2022-09-08 18:44 ` [ruby-core:109854] " RubyBugs (A Nonymous)
2022-09-10 13:24 ` zverok (Victor Shepelev) [this message]
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=redmine.journal-99113.20220910132403.1343@ruby-lang.org \
--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).