https://bugs.ruby-lang.org/https://bugs.ruby-lang.org/favicon.ico?17113305112018-01-24T21:28:42ZRuby Issue Tracking SystemRuby master - Feature #14397: public, protected and private should return their arguments instead of selfhttps://bugs.ruby-lang.org/issues/14397?journal_id=697962018-01-24T21:28:42Zusa (Usaku NAKAMURA)usa@garbagecollect.jp
<ul><li><strong>Has duplicate</strong> <i><a class="issue tracker-2 status-6 priority-4 priority-default closed" href="/issues/14396">Feature #14396</a>: public, protected and private should return their arguments instead of self</i> added</li></ul> Ruby master - Feature #14397: public, protected and private should return their arguments instead of selfhttps://bugs.ruby-lang.org/issues/14397?journal_id=698272018-01-25T12:20:30ZEregon (Benoit Daloze)
<ul><li><strong>Related to</strong> <i><a class="issue tracker-2 status-5 priority-4 priority-default closed" href="/issues/11541">Feature #11541</a>: Let attr_accessor, _reader & _writer return symbols of the defined methods</i> added</li></ul> Ruby master - Feature #14397: public, protected and private should return their arguments instead of selfhttps://bugs.ruby-lang.org/issues/14397?journal_id=698282018-01-25T12:23:35ZEregon (Benoit Daloze)
<ul></ul><p>Would it be simpler for the semantics to always return an Array of symbols?<br>
Otherwise <code>final</code> (and other potential uses) has to handle both a single Symbol and an Array of Symbol.</p>
<p>One concern is the extra allocations for the common case of a single argument given to <code>private</code>.</p> Ruby master - Feature #14397: public, protected and private should return their arguments instead of selfhttps://bugs.ruby-lang.org/issues/14397?journal_id=755342018-12-10T07:08:32Znaruse (Yui NARUSE)naruse@airemix.jp
<ul><li><strong>Target version</strong> deleted (<del><i>2.6</i></del>)</li></ul>