From: merch-redmine@jeremyevans.net
To: ruby-core@ruby-lang.org
Subject: [ruby-core:95317] [Ruby master Misc#16157] What is the correct and *portable* way to do generic delegation?
Date: Mon, 14 Oct 2019 18:10:02 +0000 (UTC) [thread overview]
Message-ID: <redmine.journal-82023.20191014181001.917a59c146d8e0fe@ruby-lang.org> (raw)
In-Reply-To: redmine.issue-16157.20190909141042@ruby-lang.org
Issue #16157 has been updated by jeremyevans0 (Jeremy Evans).
Status changed from Open to Closed
`pass_keywords` was renamed to `ruby2_keywords`. The correct and portable way to handle generic delegation is now:
```ruby
class Proxy < BasicObject
def initialize(target)
@target = target
end
def method_missing(*a, &b)
@target.send(*a, &b)
end
ruby2_keywords :method_missing if respond_to?(:ruby2_keywords, true)
end
```
Basically, keep your existing method definition, and after it add `ruby2_keywords :method_name if respond_to?(:ruby2_keywords, true)`.
That will work in all ruby versions until `ruby2_keywords` is removed. That is currently planned for after EOL of Ruby 2.6, but potentially it could stay longer.
I fixed `ruby2_keywords` so it works with `define_method`. Note that generic delegation through procs is not currently implemented, but it is not difficult to add `Proc#ruby2_keywords` if it is needed. Please request that as a feature if you want it.
----------------------------------------
Misc #16157: What is the correct and *portable* way to do generic delegation?
https://bugs.ruby-lang.org/issues/16157#change-82023
* Author: Dan0042 (Daniel DeLorme)
* Status: Closed
* Priority: Normal
* Assignee:
----------------------------------------
With the keyword argument changes in 2.7 we must now specify keyword arguments explicitly when doing generic delegation. But this change is not compatible with 2.6, where it adds an empty hash to the argument list of methods that do not need/accept keyword arguments.
To illustrate the problem:
```ruby
class ProxyWithoutKW < BasicObject
def initialize(target)
@target = target
end
def method_missing(*a, &b)
@target.send(*a, &b)
end
end
class ProxyWithKW < BasicObject
def initialize(target)
@target = target
end
def method_missing(*a, **o, &b)
@target.send(*a, **o, &b)
end
end
class Test
def args(*a) a end
def arg(a) a end
def opts(**o) o end
end
# 2.6 2.7 3.0
ProxyWithoutKW.new(Test.new).args(42) # [42] [42] [42] ok
ProxyWithoutKW.new(Test.new).arg(42) # 42 42 42 ok
ProxyWithoutKW.new(Test.new).opts(k: 42) # {:k=>42} {:k=>42} +warn [{:k=>42}] incompatible with >= 2.7
ProxyWithKW.new(Test.new).args(42) # [42, {}] [42] [42] incompatible with <= 2.6
ProxyWithKW.new(Test.new).arg(42) # error 42 42 incompatible with <= 2.6
ProxyWithKW.new(Test.new).opts(k: 42) # {:k=>42} {:k=>42} +warn {:k=>42} must ignore warning? cannot use pass_positional_hash in 2.6
```
I don't know how to solve this, so I'm asking for the **official** correct way to write portable delegation code. And by **portable** I mean code that can be used in gems that target ruby 2.6 and above.
--
https://bugs.ruby-lang.org/
next prev parent reply other threads:[~2019-10-14 18:10 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <redmine.issue-16157.20190909141042@ruby-lang.org>
2019-09-09 14:10 ` [ruby-core:94860] [Ruby master Misc#16157] What is the correct and *portable* way to do generic delegation? daniel
2019-09-09 14:22 ` [ruby-core:94861] " merch-redmine
2019-09-09 17:09 ` [ruby-core:94865] " daniel
2019-09-09 19:36 ` [ruby-core:94872] " merch-redmine
2019-09-10 14:41 ` [ruby-core:94888] " daniel
2019-09-10 16:37 ` [ruby-core:94889] " merch-redmine
2019-09-10 19:14 ` [ruby-core:94894] " daniel
2019-09-10 20:09 ` [ruby-core:94895] " merch-redmine
2019-09-11 15:36 ` [ruby-core:94904] " daniel
2019-09-11 21:25 ` [ruby-core:94909] " merch-redmine
2019-09-11 23:20 ` [ruby-core:94912] " merch-redmine
2019-09-12 2:05 ` [ruby-core:94916] " daniel
2019-09-12 12:53 ` [ruby-core:94922] " daniel
2019-09-12 15:40 ` [ruby-core:94923] " merch-redmine
2019-09-12 19:57 ` [ruby-core:94924] " daniel
2019-09-13 14:55 ` [ruby-core:94927] " daniel
2019-09-13 15:15 ` [ruby-core:94928] " merch-redmine
2019-09-13 17:00 ` [ruby-core:94931] " daniel
2019-09-13 17:54 ` [ruby-core:94933] " merch-redmine
2019-10-14 18:10 ` merch-redmine [this message]
2019-10-15 5:37 ` [ruby-core:95326] " eregontp
2019-10-15 7:23 ` [ruby-core:95328] " eregontp
2019-10-15 15:16 ` [ruby-core:95337] " merch-redmine
2019-10-15 15:49 ` [ruby-core:95339] " eregontp
2019-10-15 16:28 ` [ruby-core:95341] " merch-redmine
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-82023.20191014181001.917a59c146d8e0fe@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).