https://bugs.ruby-lang.org/https://bugs.ruby-lang.org/favicon.ico?17097754782017-03-19T23:26:43ZRuby Issue Tracking SystemRuby master - Feature #13332: Forwardable#def_instance_delegator nilhttps://bugs.ruby-lang.org/issues/13332?journal_id=636832017-03-19T23:26:43Znobu (Nobuyoshi Nakada)nobu@ruby-lang.org
<ul><li><strong>Description</strong> updated (<a title="View differences" href="/journals/63683/diff?detail_id=44362">diff</a>)</li></ul><p>I wonder how common such case is.</p>
<p>And you can override delegator/accessor methods by yourself.</p> Ruby master - Feature #13332: Forwardable#def_instance_delegator nilhttps://bugs.ruby-lang.org/issues/13332?journal_id=653912017-06-16T07:40:05Zko1 (Koichi Sasada)
<ul><li><strong>Assignee</strong> set to <i>nobu (Nobuyoshi Nakada)</i></li></ul> Ruby master - Feature #13332: Forwardable#def_instance_delegator nilhttps://bugs.ruby-lang.org/issues/13332?journal_id=668812017-09-25T08:20:55Zmatz (Yukihiro Matsumoto)matz@ruby.or.jp
<ul><li><strong>Status</strong> changed from <i>Open</i> to <i>Feedback</i></li></ul><p>The proposed solution seems to be too generic. Show us the use-case except for <code>nil for nil'. For example, it is acceptable that </code>allow_nil: true` keyword argument we see in ActiveSupport.</p>
<p>Matz.</p>