https://redmine.ruby-lang.org/https://redmine.ruby-lang.org/favicon.ico?17113305112020-01-26T02:12:29ZRuby Issue Tracking SystemRuby master - Misc #16561: DevelopersMeeting20200227Japanhttps://redmine.ruby-lang.org/issues/16561?journal_id=840552020-01-26T02:12:29Zmame (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 #16561: DevelopersMeeting20200227Japanhttps://redmine.ruby-lang.org/issues/16561?journal_id=840562020-01-26T02:13:08Zmame (Yusuke Endoh)mame@ruby-lang.org
<ul><li><strong>Description</strong> updated (<a title="View differences" href="/journals/84056/diff?detail_id=56273">diff</a>)</li></ul> Ruby master - Misc #16561: DevelopersMeeting20200227Japanhttps://redmine.ruby-lang.org/issues/16561?journal_id=840572020-01-26T16:12:17Zznz (Kazuhiro NISHIYAMA)
<ul></ul><ul>
<li>[Misc <a class="issue tracker-5 status-5 priority-4 priority-default closed" title="Misc: How about stopping new *.tar.bz2 releases? (Closed)" href="https://redmine.ruby-lang.org/issues/16483">#16483</a>] How about stopping new *.tar.bz2 releases? (znz)
<ul>
<li>Stop new bz2 releases, keep already existing bz2 releases.</li>
</ul>
</li>
</ul> Ruby master - Misc #16561: DevelopersMeeting20200227Japanhttps://redmine.ruby-lang.org/issues/16561?journal_id=840912020-01-27T03:56:47Zjeremyevans0 (Jeremy Evans)merch-redmine@jeremyevans.net
<ul></ul><ul>
<li>[Feature <a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Bug: descendants of a module don't gain its future ancestors, but descendants of a class, do (Closed)" href="https://redmine.ruby-lang.org/issues/9573">#9573</a>] descendants of a module don't gain its future ancestors, but descendants of a class, do (jeremyevans0)
<ul>
<li>A patch exists for Module#include that passes make check, is it OK to merge?</li>
<li>A patch exists for Module#prepend that still has many issues to resolve and requires creating origin classes for almost all modules, do we want to try to support this feature for Module#prepend?</li>
</ul>
</li>
<li>[Feature <a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Bug: Should Zlib::GzipReader#ungetc accept nil? (Closed)" href="https://redmine.ruby-lang.org/issues/13675">#13675</a>] Should Zlib::GzipReader#ungetc accept nil? (jeremyevans0)
<ul>
<li>Has matz decided whether to fix IO#ungetc? If so, is the patch OK?</li>
</ul>
</li>
<li>[Feature <a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Bug: [PATCH] Kernel.global_variables should observe $~. (Closed)" href="https://redmine.ruby-lang.org/issues/11304">#11304</a>] [PATCH] Kernel.global_variables should observe $~. (jeremyevans0)
<ul>
<li>Do we want to modify the behavior of Kernel.global_variables for $1, $2, etc.</li>
<li>Do we want defined? for $& $' $+ $1 $2 to depend on whether $~ is set?</li>
<li>Should defined? for global variable aliases always be the same as what they alias?</li>
</ul>
</li>
</ul> Ruby master - Misc #16561: DevelopersMeeting20200227Japanhttps://redmine.ruby-lang.org/issues/16561?journal_id=840932020-01-27T09:39:52Zbyroot (Jean Boussier)byroot@ruby-lang.org
<ul></ul><ul>
<li>[Feature <a class="issue tracker-2 status-1 priority-4 priority-default" title="Feature: Deduplicate Regexp literals (Open)" href="https://redmine.ruby-lang.org/issues/16557">#16557</a>] Deduplicate Regexp literals (byroot)
<ul>
<li>[<a class="issue tracker-2 status-5 priority-4 priority-default closed" title="Feature: Regexp literals should be frozen (Closed)" href="https://redmine.ruby-lang.org/issues/16377">#16377</a>] made literal regexps frozen, so they can be deduplicated without further backward compatibility change</li>
<li>The estimated memory saving is about <code>1.4 MB</code> on Redmine (and pretty much all Rails apps).</li>
</ul>
</li>
</ul> Ruby master - Misc #16561: DevelopersMeeting20200227Japanhttps://redmine.ruby-lang.org/issues/16561?journal_id=841542020-02-04T10:36:41Zsawa (Tsuyoshi Sawada)
<ul></ul><ul>
<li>[Feature <a class="issue tracker-2 status-7 priority-4 priority-default closed" title="Feature: `Kernel#case?` (Feedback)" href="https://redmine.ruby-lang.org/issues/15722">#15722</a>] <code>Kernel#case?</code> (sawa)
<ul>
<li><code>"foo".case?(Symbol, String) # => true</code></li>
</ul>
</li>
</ul> Ruby master - Misc #16561: DevelopersMeeting20200227Japanhttps://redmine.ruby-lang.org/issues/16561?journal_id=842312020-02-11T23:02:54Zkirs (Kir Shatrov)shatrov@me.com
<ul></ul><ul>
<li>[Feature <a class="issue tracker-2 status-5 priority-4 priority-default closed" title="Feature: Socket.getaddrinfo cannot be interrupted by Timeout.timeout (Closed)" href="https://redmine.ruby-lang.org/issues/16476">#16476</a>] Socket.getaddrinfo cannot be interrupted by Timeout.timeout (kirs)
<ul>
<li>Would we be happy with the proposed solution leveraging <code>getaddrinfo_a</code>? If yes, is it good to merge?</li>
</ul>
</li>
</ul> Ruby master - Misc #16561: DevelopersMeeting20200227Japanhttps://redmine.ruby-lang.org/issues/16561?journal_id=843042020-02-18T21:19:19ZEregon (Benoit Daloze)
<ul></ul><ul>
<li>[Feature <a class="issue tracker-2 status-5 priority-4 priority-default closed" title="Feature: Fixing *args-delegation in Ruby 2.7: ruby2_keywords semantics by default in 2.7.1 (Closed)" href="https://redmine.ruby-lang.org/issues/16463">#16463</a>] Fixing *args-delegation in Ruby 2.7: ruby2_keywords semantics by default in 2.7.1 (eregon)
<ul>
<li>It would be good to decide.</li>
<li>We can also discuss it at the RubyKaigi dev meeting, but is that not too late for 2.7.1?</li>
</ul>
</li>
</ul> Ruby master - Misc #16561: DevelopersMeeting20200227Japanhttps://redmine.ruby-lang.org/issues/16561?journal_id=843112020-02-19T17:57:23ZDan0042 (Daniel DeLorme)
<ul></ul><ul>
<li>[Feature <a class="issue tracker-2 status-1 priority-4 priority-default" title="Feature: Staged warnings and better compatibility for keyword arguments in 2.7.1 (Open)" href="https://redmine.ruby-lang.org/issues/16511">#16511</a>] Staged warnings and better compatibility for keyword arguments in 2.7.1 (Dan0042)
<ul>
<li>All the benefits of separation of keyword/positional arguments.</li>
<li>Less disruptive migration in the near term; only the strict necessary breaks next year, fewer gems to upgrade.</li>
<li>Fewer incompatibilities, inconsistencies, and side effects. (specifics in <a href="https://bugs.ruby-lang.org/issues/16511#note-12" class="external">note 12</a>)</li>
<li>This is not theoretical, I've implemented it: <a href="https://git.io/JvWXA" class="external">https://git.io/JvWXA</a> (last 4 commits; other commits with "refactor" are not strictly relevant)</li>
<li>The implementation touches a lot of code; it's well-tested, but maybe too much, too late.</li>
<li>For some reason it seems no one understands my proposal? I can volunteer to answer questions at the dev meeting... if desired.</li>
</ul>
</li>
</ul> Ruby master - Misc #16561: DevelopersMeeting20200227Japanhttps://redmine.ruby-lang.org/issues/16561?journal_id=844192020-02-28T03:35:24Zmame (Yusuke Endoh)mame@ruby-lang.org
<ul><li><strong>Status</strong> changed from <i>Open</i> to <i>Closed</i></li></ul>