https://bugs.ruby-lang.org/https://bugs.ruby-lang.org/favicon.ico?17113305112021-10-25T09:11:57ZRuby Issue Tracking SystemRuby master - Misc #18266: DevelopersMeeting20211118Japanhttps://bugs.ruby-lang.org/issues/18266?journal_id=942972021-10-25T09:11:57Zmame (Yusuke Endoh)mame@ruby-lang.org
<ul><li><strong>Related to</strong> <i><a class="issue tracker-5 status-1 priority-4 priority-default" href="/issues/14770">Misc #14770</a>: [META] DevelopersMeeting</i> added</li></ul> Ruby master - Misc #18266: DevelopersMeeting20211118Japanhttps://bugs.ruby-lang.org/issues/18266?journal_id=942982021-10-25T09:17:49Zzverok (Victor Shepelev)zverok.offline@gmail.com
<ul></ul><ul>
<li>[Feature <a class="issue tracker-2 status-1 priority-4 priority-default" title="Feature: Enumerator::Lazy#partition (Open)" href="https://bugs.ruby-lang.org/issues/18262">#18262</a>] <code>Enumerator::Lazy#partition</code> (zverok)
<ul>
<li>Part of the effort to make <code>Lazy</code> more natural: <code>#partition</code> to return two lazy enumerators</li>
</ul>
</li>
</ul> Ruby master - Misc #18266: DevelopersMeeting20211118Japanhttps://bugs.ruby-lang.org/issues/18266?journal_id=943162021-10-26T02:28:21Zshugo (Shugo Maeda)
<ul></ul><ul>
<li>[Feature <a class="issue tracker-2 status-5 priority-4 priority-default closed" title="Feature: Module#defined_refinements (Closed)" href="https://bugs.ruby-lang.org/issues/12737">#12737</a>] Module#defined_refinements (shugo)
<ul>
<li>It's good to have for debugging purposes. Users can see refinements defined in a module in irb etc. without reading code.</li>
</ul>
</li>
<li>[Feature <a class="issue tracker-2 status-5 priority-4 priority-default closed" title="Feature: Module.used_refinements to list refinement modules (Closed)" href="https://bugs.ruby-lang.org/issues/14332">#14332</a>] Module.used_refinements to list refinement modules (shugo)
<ul>
<li>It's good to have for debugging purposes. Users can see all activated refinements in a given scope.</li>
</ul>
</li>
</ul> Ruby master - Misc #18266: DevelopersMeeting20211118Japanhttps://bugs.ruby-lang.org/issues/18266?journal_id=943262021-10-26T10:39:12Zshugo (Shugo Maeda)
<ul></ul><ul>
<li>[Bug <a class="issue tracker-2 status-5 priority-4 priority-default closed" title="Feature: Refinement#{extend_object,append_features,prepend_features} should be removed (Closed)" href="https://bugs.ruby-lang.org/issues/18270">#18270</a>] Refinement#{extend_object,append_features,prepend_features} should be removed
<ul>
<li>Refinements are different from normal modules, so it's potentially dangerous to use refinements as mixins.</li>
<li>Why not deprecate them in Ruby 3.1, and remove them in Ruby 3.2.</li>
</ul>
</li>
</ul> Ruby master - Misc #18266: DevelopersMeeting20211118Japanhttps://bugs.ruby-lang.org/issues/18266?journal_id=943282021-10-26T14:44:54ZDan0042 (Daniel DeLorme)
<ul></ul><ul>
<li>[Feature <a class="issue tracker-2 status-1 priority-4 priority-default" title="Feature: Hash#partition should return hashes (Open)" href="https://bugs.ruby-lang.org/issues/16252">#16252</a>] Hash#partition should return hashes (dan0042)
<ul>
<li>More consistent with <code>select</code>/<code>reject</code>
</li>
<li>More in line with existing usage (most people seem to convert the results to hashes)</li>
<li>More efficient than arrays of arrays</li>
<li>Mostly compatible</li>
</ul>
</li>
</ul> Ruby master - Misc #18266: DevelopersMeeting20211118Japanhttps://bugs.ruby-lang.org/issues/18266?journal_id=944762021-11-04T13:16:53ZEregon (Benoit Daloze)
<ul></ul><ul>
<li>[Misc <a class="issue tracker-2 status-5 priority-4 priority-default closed" title="Feature: NoMethodError#message uses a lot of CPU/is really expensive to call (Closed)" href="https://bugs.ruby-lang.org/issues/18285">#18285</a>] NoMethodError#message uses a lot of CPU/is really expensive to call (eregon)
<ul>
<li>OK to do <a href="https://bugs.ruby-lang.org/issues/18285#note-11" class="external">https://bugs.ruby-lang.org/issues/18285#note-11</a> and no longer call custom #inspect for NoMethodError?</li>
<li>Same for NameError?</li>
</ul>
</li>
<li>[Bug <a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Bug: Ractor.make_shareable does not freeze the receiver of a Proc but allows accessing ivars of it (Closed)" href="https://bugs.ruby-lang.org/issues/18243">#18243</a>] Ractor.make_shareable does not freeze the receiver of a Proc but allows accessing ivars of it (eregon)
<ul>
<li>How about this approach to fix it <a href="https://bugs.ruby-lang.org/issues/18243#note-9" class="external">https://bugs.ruby-lang.org/issues/18243#note-9</a>?</li>
<li>I think passing a Proc with a non-shareable <code>self</code> to a Ractor is highly confusing semantically and in practice, and it's prone to bugs.</li>
</ul>
</li>
</ul> Ruby master - Misc #18266: DevelopersMeeting20211118Japanhttps://bugs.ruby-lang.org/issues/18266?journal_id=944912021-11-05T08:55:34Zbyroot (Jean Boussier)byroot@ruby-lang.org
<ul></ul><ul>
<li>[Feature <a class="issue tracker-2 status-5 priority-4 priority-default closed" title="Feature: Class#subclasses (Closed)" href="https://bugs.ruby-lang.org/issues/18273">#18273</a>] <code>Class#subclasses</code>
<ul>
<li>Something we forgot to discuss as part of [Feature <a class="issue tracker-2 status-1 priority-4 priority-default" title="Feature: Class.descendants (Open)" href="https://bugs.ruby-lang.org/issues/14394">#14394</a>].</li>
<li>There are cases where you only want direct subclasses, not the whole tree.</li>
<li>Can either be <code>Class#subclasses</code> like in Active Record.</li>
<li>Or could be a boolean parameter on <code>descendants</code>.</li>
</ul>
</li>
</ul> Ruby master - Misc #18266: DevelopersMeeting20211118Japanhttps://bugs.ruby-lang.org/issues/18266?journal_id=944972021-11-05T18:42:58ZEregon (Benoit Daloze)
<ul></ul><ul>
<li>[Feature <a class="issue tracker-2 status-5 priority-4 priority-default closed" title="Feature: Support nil value for sort in Dir.glob (Closed)" href="https://bugs.ruby-lang.org/issues/18287">#18287</a>] Support nil value for sort in Dir.glob (eregon)
<ul>
<li>Let's be consistent for core methods and treat <code>nil</code> as <code>false</code>, or raise if not boolean.</li>
</ul>
</li>
</ul> Ruby master - Misc #18266: DevelopersMeeting20211118Japanhttps://bugs.ruby-lang.org/issues/18266?journal_id=945172021-11-08T18:01:00Zjeremyevans0 (Jeremy Evans)merch-redmine@jeremyevans.net
<ul></ul><ul>
<li>[Feature <a class="issue tracker-2 status-5 priority-4 priority-default closed" title="Feature: load should provide a way to specify the top-level module (Closed)" href="https://bugs.ruby-lang.org/issues/6210">#6210</a>] load should provide a way to specify the top-level module (jeremyevans0)
<ul>
<li>This is fairly easy to implement in a backwards compatible manner, and seems useful.</li>
<li>Are we OK adding this feature? If so, is the pull request acceptable?</li>
</ul>
</li>
<li>[Feature <a class="issue tracker-2 status-5 priority-4 priority-default closed" title="Feature: anonymous block forwarding (Closed)" href="https://bugs.ruby-lang.org/issues/11256">#11256</a>] anonymous block forwarding (jeremyevans0)
<ul>
<li>This was accepted by <a class="user active user-mention" href="https://bugs.ruby-lang.org/users/13">@matz (Yukihiro Matsumoto)</a> four years ago, but never committed.</li>
<li>I've created a new working version based on patches from <a class="user active user-mention" href="https://bugs.ruby-lang.org/users/4">@nobu (Nobuyoshi Nakada)</a> and <a class="user active user-mention" href="https://bugs.ruby-lang.org/users/18">@mame (Yusuke Endoh)</a>.</li>
<li>There should be no backwards compatibility issues, as the proposed syntax is currently invalid.</li>
<li>Is it OK to add this feature? If so, is the pull request acceptable?</li>
</ul>
</li>
<li>[Feature <a class="issue tracker-2 status-1 priority-4 priority-default" title="Feature: Add methods allow us to get visibility from Method and UnboundMethod object. (Open)" href="https://bugs.ruby-lang.org/issues/11689">#11689</a>] Add methods allow us to get visibility from Method and UnboundMethod object. (jeremyevans0)
<ul>
<li>As requested by <a class="user active user-mention" href="https://bugs.ruby-lang.org/users/13">@matz (Yukihiro Matsumoto)</a>, I put together a patch for #public?, #private?, and #protected?.</li>
<li>Do we want to use this approach, or do we want to reconsider the #visibility method that returns a symbol?</li>
<li>If we want to use this approach, is the pull request acceptable?</li>
</ul>
</li>
<li>[Feature <a class="issue tracker-2 status-5 priority-4 priority-default closed" title="Feature: Make "private" return the arguments again, for chaining (Closed)" href="https://bugs.ruby-lang.org/issues/12495">#12495</a>] Make "private" return the arguments again, for chaining (jeremyevans0)
<ul>
<li>This seems useful, and the backwards compatible issues are quite small.</li>
<li>Are we OK adding this feature? If so, is the pull request acceptable?</li>
</ul>
</li>
<li>[Feature <a class="issue tracker-2 status-5 priority-4 priority-default closed" title="Feature: Add block or filtered forms of Kernel#caller to allow early bail-out (Closed)" href="https://bugs.ruby-lang.org/issues/16663">#16663</a>] Add block or filtered forms of Kernel#caller to allow early bail-out (jeremyevans0)
<ul>
<li>Currently it is not possible to generate a partial backtrace without knowing how many frames you need up front.</li>
<li>This feature allows the production of partial backtraces without that knowledge.</li>
<li>For example, you can use it to return the only the first frame that meets some criteria.</li>
<li>There shouldn't be any backwards compatibility issues, as caller/caller_locations does not currently use a block.</li>
<li>Are we OK adding this feature? If so, is the pull request acceptable?</li>
</ul>
</li>
</ul> Ruby master - Misc #18266: DevelopersMeeting20211118Japanhttps://bugs.ruby-lang.org/issues/18266?journal_id=945642021-11-10T12:02:33Zioquatix (Samuel Williams)samuel@oriontransfer.net
<ul></ul><ul>
<li>[Bug <a class="issue tracker-2 status-5 priority-4 priority-default closed" title="Feature: Custom exception formatting should override `Exception#full_message`. (Closed)" href="https://bugs.ruby-lang.org/issues/18296">#18296</a>] Custom exception formatting should override <code>Exception#full_message</code>.
<ul>
<li>(mame: you need to write your comment)</li>
</ul>
</li>
</ul> Ruby master - Misc #18266: DevelopersMeeting20211118Japanhttps://bugs.ruby-lang.org/issues/18266?journal_id=946622021-11-15T22:31:31Zduerst (Martin Dürst)duerst@it.aoyama.ac.jp
<ul></ul><ul>
<li>[Feature <a class="issue tracker-2 status-7 priority-4 priority-default closed" title="Feature: How to deal with Trojan Source vulnerability (Feedback)" href="https://bugs.ruby-lang.org/issues/18336">#18336</a>] How to deal with Trojan Source vulnerability
<ul>
<li>For [A], Bidi characters, I think "wait and see" may be the right decision, but it should be explicit.</li>
</ul>
</li>
<li>[Feature <a class="issue tracker-1 status-2 priority-4 priority-default" title="Bug: Ruby allows zero-width characters in identifiers (Assigned)" href="https://bugs.ruby-lang.org/issues/18337">#18337</a>] Ruby allows zero-width characters in identifiers
<ul>
<li>Suggest to use <a href="https://www.unicode.org/reports/tr31/" class="external">https://www.unicode.org/reports/tr31/</a>, to catch up with other languages.</li>
</ul>
</li>
</ul> Ruby master - Misc #18266: DevelopersMeeting20211118Japanhttps://bugs.ruby-lang.org/issues/18266?journal_id=946642021-11-16T01:24:22Zmame (Yusuke Endoh)mame@ruby-lang.org
<ul></ul><p>Warning: Please read the instruction carefully. You must briefly write what you want us to discuss as a comment. It is ideal if we can start discussing without reading the ticket itself.</p> Ruby master - Misc #18266: DevelopersMeeting20211118Japanhttps://bugs.ruby-lang.org/issues/18266?journal_id=946702021-11-16T08:55:40Zbyroot (Jean Boussier)byroot@ruby-lang.org
<ul></ul><p>[Feature <a class="issue tracker-2 status-5 priority-4 priority-default closed" title="Feature: GVL instrumentation API (Closed)" href="https://bugs.ruby-lang.org/issues/18339">#18339</a>] GVL instrumentation API</p>
<ul>
<li>I'd like 3 new internal tracepoints: <code>RUBY_INTERNAL_EVENT_GVL_ACQUIRE_ENTER</code>, <code>RUBY_INTERNAL_EVENT_GVL_ACQUIRE_EXIT</code>, <code>RUBY_INTERNAL_EVENT_GVL_RELEASE</code>
</li>
<li>It would be also very useful if the number of waiting thread was part of the hook arguments.</li>
<li>It would allow to instrument the GVL which is a key metric for threaded environments, and to tune concurrency in applications.</li>
<li>Is the feature acceptable?</li>
<li>Any performance concerns when no hook is registered?</li>
</ul> Ruby master - Misc #18266: DevelopersMeeting20211118Japanhttps://bugs.ruby-lang.org/issues/18266?journal_id=947432021-11-18T14:32:25Zmame (Yusuke Endoh)mame@ruby-lang.org
<ul><li><strong>Description</strong> updated (<a title="View differences" href="/journals/94743/diff?detail_id=61220">diff</a>)</li><li><strong>Status</strong> changed from <i>Open</i> to <i>Closed</i></li></ul> Ruby master - Misc #18266: DevelopersMeeting20211118Japanhttps://bugs.ruby-lang.org/issues/18266?journal_id=947472021-11-18T14:35:30Zmame (Yusuke Endoh)mame@ruby-lang.org
<ul><li><strong>Description</strong> updated (<a title="View differences" href="/journals/94747/diff?detail_id=61224">diff</a>)</li></ul>