https://redmine.ruby-lang.org/https://redmine.ruby-lang.org/favicon.ico?17113305112021-11-18T14:32:51ZRuby Issue Tracking SystemRuby master - Misc #18346: DevelopersMeeting20211209Japanhttps://redmine.ruby-lang.org/issues/18346?journal_id=947452021-11-18T14:32:51Zmame (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 #18346: DevelopersMeeting20211209Japanhttps://redmine.ruby-lang.org/issues/18346?journal_id=948302021-11-23T06:22:37Zk0kubun (Takashi Kokubun)takashikkbn@gmail.com
<ul></ul><ul>
<li>[Feature <a class="issue tracker-2 status-5 priority-4 priority-default closed" title="Feature: Let --jit enable YJIT on supported platforms (Closed)" href="https://redmine.ruby-lang.org/issues/18349">#18349</a>] Let --jit enable YJIT on supported platforms (k0kubun)
<ul>
<li>Any concerns? Can we do this from Ruby 3.1?</li>
</ul>
</li>
</ul> Ruby master - Misc #18346: DevelopersMeeting20211209Japanhttps://redmine.ruby-lang.org/issues/18346?journal_id=949052021-11-25T16:32:57ZEregon (Benoit Daloze)
<ul></ul><ul>
<li>[Feature <a class="issue tracker-2 status-5 priority-4 priority-default closed" title="Feature: Provide a public WeakMap that compares by equality rather than by identity (Closed)" href="https://redmine.ruby-lang.org/issues/16038">#16038</a>] Provide a public WeakMap that compares by equality rather than by identity (eregon)
<ul>
<li>This is necessary to have access to a weak-keys map on TruffleRuby/JRuby. There are many use cases:, notably <a href="https://github.com/rails/rails/pull/43723" class="external">this PR in Rails</a> and all the reasons WeakHashMap is used in Java code.</li>
</ul>
</li>
</ul> Ruby master - Misc #18346: DevelopersMeeting20211209Japanhttps://redmine.ruby-lang.org/issues/18346?journal_id=949422021-11-29T16:59:29Zjeremyevans0 (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: Support anonymous rest and keyword rest argument forwarding (Closed)" href="https://redmine.ruby-lang.org/issues/18351">#18351</a>] Support anonymous rest and keyword rest argument forwarding (jeremyevans0)
<ul>
<li>I think this is a natural addition after the addition of anonymous block forwarding in <a class="issue tracker-2 status-5 priority-4 priority-default closed" title="Feature: anonymous block forwarding (Closed)" href="https://redmine.ruby-lang.org/issues/11256">#11256</a>.</li>
<li>Is it OK to support this syntax? If so, is the patch 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://redmine.ruby-lang.org/issues/16663">#16663</a>] Add block or filtered forms of Kernel#caller to allow early bail-out (jeremyevans0)
<ul>
<li>Two possible method names are find_caller and each_caller.</li>
<li>find_caller optimizes for the case where the first matching frame will be returned.</li>
<li>each_caller is more general, always iterating unless there is a non-local exit (break/return).</li>
<li>Are either of these names acceptable? If so, which method name should be used?</li>
</ul>
</li>
<li>[Feature <a class="issue tracker-2 status-5 priority-4 priority-default closed" title="Feature: `Class#instance` (Closed)" href="https://redmine.ruby-lang.org/issues/12084">#12084</a>] <code>Class#instance</code> (jeremyevans0)
<ul>
<li>This should be simple to implement, since a singleton class keeps a reference to the instance.</li>
<li>Are we OK adding this feature? If so, is the method name acceptable, or do we want <code>singleton_instance</code>?</li>
<li>If called on a non-singleton class, should TypeError be raised?</li>
<li>For TrueClass, FalseClass, and NilClass, should it return true, false, and nil?</li>
</ul>
</li>
<li>[Bug <a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Bug: Pathname#join has different behaviour to File.join (Closed)" href="https://redmine.ruby-lang.org/issues/14891">#14891</a>] Pathname#join has different behaviour to File.join (jeremyevans0)
<ul>
<li>I agree with <a class="user active user-mention" href="https://redmine.ruby-lang.org/users/14">@znz (Kazuhiro NISHIYAMA)</a> that this behavior is expected.</li>
<li>Can this be closed?</li>
</ul>
</li>
<li>[Bug <a class="issue tracker-1 status-7 priority-4 priority-default closed" title="Bug: IO#reopen fails after EPIPE (Feedback)" href="https://redmine.ruby-lang.org/issues/14434">#14434</a>] IO#reopen fails after EPIPE (jeremyevans0)
<ul>
<li>I'm not sure whether this behavior is a bug.</li>
<li>The behavior has existed since Ruby 1.9 (no failure in 1.8.7).</li>
<li>Can we decide whether this behavior is expected or a bug?</li>
</ul>
</li>
</ul> Ruby master - Misc #18346: DevelopersMeeting20211209Japanhttps://redmine.ruby-lang.org/issues/18346?journal_id=949872021-11-30T14:37:48ZEregon (Benoit Daloze)
<ul></ul><ul>
<li>[Feature <a class="issue tracker-2 status-5 priority-4 priority-default closed" title="Feature: Call Exception#full_message to print exceptions reaching the top-level (Closed)" href="https://redmine.ruby-lang.org/issues/18370">#18370</a>] Call Exception#full_message to print exceptions reaching the top-level (eregon)
<ul>
<li>Improve consistency in how exceptions are shown, and makes it easier to evolve exception formatting.</li>
<li>OK to do?</li>
</ul>
</li>
</ul> Ruby master - Misc #18346: DevelopersMeeting20211209Japanhttps://redmine.ruby-lang.org/issues/18346?journal_id=949892021-11-30T15:47:48Zpeterzhu2118 (Peter Zhu)peter@peterzhu.ca
<ul></ul><ul>
<li>[Feature <a class="issue tracker-2 status-5 priority-4 priority-default closed" title="Feature: Add GC.stat_pool for Variable Width Allocation (Closed)" href="https://redmine.ruby-lang.org/issues/18364">#18364</a>] Add <code>GC.stat_pool</code> for Variable Width Allocation (peterzhu2118)
<ul>
<li>This feature will allow accessing stats for memory pools through Ruby. This will be especially useful for the Variable Width Allocation feature.</li>
<li>Should we extend <code>GC.stat</code> to return stats for memory pools or create a new method such as <code>GC.stat_pool</code>?</li>
<li>Is <code>GC.stat_pool</code> a good name?</li>
</ul>
</li>
</ul> Ruby master - Misc #18346: DevelopersMeeting20211209Japanhttps://redmine.ruby-lang.org/issues/18346?journal_id=951322021-12-03T23:19:04Zbyroot (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: Add a Module#const_added callback (Closed)" href="https://redmine.ruby-lang.org/issues/17881">#17881</a>] Add a Module#const_added callback
<ul>
<li>Would allow the Zeitwerk autoloader to no longer use tracepoint.</li>
<li>The main problem with Zeitwerk using tracepoint is that since tracepoint callbacks are not "reentrant" Zeitwerk is partially broken when using a debugger, e.g. <a href="https://github.com/ruby/debug/issues/408" class="external">https://github.com/ruby/debug/issues/408</a>
</li>
<li>This cause lots of confusion for users.</li>
<li>Could alternatively be <code>Module#module_defined</code>, to only be called for <code>Module/Class</code>
</li>
</ul>
</li>
</ul> Ruby master - Misc #18346: DevelopersMeeting20211209Japanhttps://redmine.ruby-lang.org/issues/18346?journal_id=951372021-12-04T08:31:51Zbyroot (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: Allow some reentrancy during TracePoint events (Closed)" href="https://redmine.ruby-lang.org/issues/15912">#15912</a>] Allow some reentrancy during TracePoint event
<ul>
<li>Alternative to <code>Module#const_added</code> for fixing the Zeitwerk and debuggers combinaison.</li>
<li><a class="user active user-mention" href="https://redmine.ruby-lang.org/users/17">@ko1 (Koichi Sasada)</a> proposed <code>Tracepoint#reopen(&block)</code> so that debuggers can yield to the user with that.</li>
<li>Potentially with a list of reopened events: <code>tp.reopen(:class) { "do stuff" }</code>
</li>
</ul>
</li>
</ul> Ruby master - Misc #18346: DevelopersMeeting20211209Japanhttps://redmine.ruby-lang.org/issues/18346?journal_id=951892021-12-07T04:26:16Zshugo (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://redmine.ruby-lang.org/issues/12737">#12737</a>] Module#defined_refinements
<ul>
<li>Is the name Module#refinements acceptable?
<ul>
<li>It's consistent with Module#constants.</li>
<li>Other candidates: configured_refinements, contained_refinements, defined_refinements</li>
</ul>
</li>
<li>Is it OK to return an Array instead of Hash?
<ul>
<li>The target class of a refinement can be obtained by another new method Refinement#refined_class.</li>
</ul>
</li>
<li>I'd like to add Module#refinements and Refinement#refined_class after the release of Ruby 3.1.</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://redmine.ruby-lang.org/issues/14332">#14332</a>] Module.used_refinements to list refinement modules
<ul>
<li>eregon suggested to add it soon, but It may be too late to add it in Ruby 3.1.</li>
</ul>
</li>
</ul> Ruby master - Misc #18346: DevelopersMeeting20211209Japanhttps://redmine.ruby-lang.org/issues/18346?journal_id=951922021-12-07T06:07:18Znobu (Nobuyoshi Nakada)nobu@ruby-lang.org
<ul></ul><ul>
<li>
<p>[Feature <a class="issue tracker-2 status-5 priority-4 priority-default closed" title="Feature: Time.new to parse a string (Closed)" href="https://redmine.ruby-lang.org/issues/18033">#18033</a>] <a href="https://bugs.ruby-lang.org/issues/18033" class="external">https://bugs.ruby-lang.org/issues/18033</a></p>
<ul>
<li>
<code>Time.at("2021-12-09")</code> instead of <code>Time.new</code>.</li>
<li>Other new methods: <code>Time.try_convert</code> or <code>Time.iso</code>.</li>
</ul>
</li>
<li>
<p>[Feature <a class="issue tracker-2 status-5 priority-4 priority-default closed" title="Feature: Split `Random::Formatter` from securerandom (Closed)" href="https://redmine.ruby-lang.org/issues/18190">#18190</a>] Split <code>Random::Formatter</code> from securerandom</p>
<ul>
<li>Already <a href="https://github.com/ruby/securerandom/pull/7" class="external">ruby/securerandom#7</a> has been merged.</li>
</ul>
</li>
<li>
<p>[Feature <a class="issue tracker-2 status-5 priority-4 priority-default closed" title="Feature: make SecureRandom.choose public (Closed)" href="https://redmine.ruby-lang.org/issues/18183">#18183</a>] make <code>SecureRandom.choose</code> public</p>
</li>
</ul> Ruby master - Misc #18346: DevelopersMeeting20211209Japanhttps://redmine.ruby-lang.org/issues/18346?journal_id=951952021-12-07T06:43:46Zsawa (Tsuyoshi Sawada)
<ul></ul><ul>
<li>[Feature <a class="issue tracker-2 status-1 priority-4 priority-default" title="Feature: Kernel.#Time (Open)" href="https://redmine.ruby-lang.org/issues/18331">#18331</a>] Kernel.#Time (sawa)
<ul>
<li>Introduce <code>Kernel.#Time</code> {instead of/in addition to} extending <code>Time.new</code> as in <a class="issue tracker-2 status-5 priority-4 priority-default closed" title="Feature: Time.new to parse a string (Closed)" href="https://redmine.ruby-lang.org/issues/18033">#18033</a>.</li>
<li>Similar methods like <code>Kernel#.Integer</code> are used to parse strings, and this is a good fit for <code>Time</code>.</li>
</ul>
</li>
</ul> Ruby master - Misc #18346: DevelopersMeeting20211209Japanhttps://redmine.ruby-lang.org/issues/18346?journal_id=952612021-12-09T12:30:40Zmame (Yusuke Endoh)mame@ruby-lang.org
<ul><li><strong>Description</strong> updated (<a title="View differences" href="/journals/95261/diff?detail_id=61467">diff</a>)</li><li><strong>Status</strong> changed from <i>Open</i> to <i>Closed</i></li></ul>