https://redmine.ruby-lang.org/https://redmine.ruby-lang.org/favicon.ico?17113305112018-09-16T13:22:03ZRuby Issue Tracking SystemRuby master - Misc #15129: DevelopersMeeting20181010Japanhttps://redmine.ruby-lang.org/issues/15129?journal_id=740602018-09-16T13:22:03Zmame (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 #15129: DevelopersMeeting20181010Japanhttps://redmine.ruby-lang.org/issues/15129?journal_id=740612018-09-16T13:28:05Zmame (Yusuke Endoh)mame@ruby-lang.org
<ul><li><strong>Description</strong> updated (<a title="View differences" href="/journals/74061/diff?detail_id=49893">diff</a>)</li></ul> Ruby master - Misc #15129: DevelopersMeeting20181010Japanhttps://redmine.ruby-lang.org/issues/15129?journal_id=740622018-09-16T14:19:59Zmame (Yusuke Endoh)mame@ruby-lang.org
<ul><li><strong>Description</strong> updated (<a title="View differences" href="/journals/74062/diff?detail_id=49894">diff</a>)</li></ul> Ruby master - Misc #15129: DevelopersMeeting20181010Japanhttps://redmine.ruby-lang.org/issues/15129?journal_id=740632018-09-16T14:29:18Zmame (Yusuke Endoh)mame@ruby-lang.org
<ul><li><strong>Description</strong> updated (<a title="View differences" href="/journals/74063/diff?detail_id=49895">diff</a>)</li></ul> Ruby master - Misc #15129: DevelopersMeeting20181010Japanhttps://redmine.ruby-lang.org/issues/15129?journal_id=740922018-09-18T16:24:48Zgreggzst (Grzegorz Jakubiak)
<ul></ul><p><a href="https://bugs.ruby-lang.org/issues/15123" class="external">[Feature #15123]</a> Enumerable#compact proposal (greggzst)<br>
It simplifies working with large and small collections so one doesn't have to remember that can't use <code>#compact</code> when enumerator is returned and have to fall back to <code>#reject(:nil?)</code>.</p> Ruby master - Misc #15129: DevelopersMeeting20181010Japanhttps://redmine.ruby-lang.org/issues/15129?journal_id=741772018-09-24T16:16:27Zshevegen (Robert A. Heiler)shevegen@gmail.com
<ul></ul><p>Feature suggestion <a class="issue tracker-2 status-1 priority-4 priority-default" title="Feature: Introducing the short form of `STDERR.puts expr.inspect`. (Open)" href="https://redmine.ruby-lang.org/issues/15112">#15112</a> Introduce the new singleton method STDERR.p (by Kenta Murata)<br>
I am mostly curious what the ruby core team thinks about Kenta Murata's proposal; it probably will not take too much time away discussing it briefly, since the scope is small.</p> Ruby master - Misc #15129: DevelopersMeeting20181010Japanhttps://redmine.ruby-lang.org/issues/15129?journal_id=741942018-09-25T22:20:16Zrafaelfranca (Rafael França)rafael@franca.dev
<ul></ul><ul>
<li>[Feature <a class="issue tracker-2 status-6 priority-4 priority-default closed" title="Feature: Module#=== should call #kind_of? on the object rather than rb_obj_is_kind_of which only searches ... (Rejected)" href="https://redmine.ruby-lang.org/issues/11505">#11505</a>] Module#=== should call #kind_of? on the object rather than rb_obj_is_kind_of which only searches the ancestor heirarchy
<ul>
<li>This would allow patterns as Decorator and Proxy to work with case statements.</li>
</ul>
</li>
</ul> Ruby master - Misc #15129: DevelopersMeeting20181010Japanhttps://redmine.ruby-lang.org/issues/15129?journal_id=742092018-09-26T21:25:04Zgreggzst (Grzegorz Jakubiak)
<ul></ul><p><a href="https://bugs.ruby-lang.org/issues/14912" class="external">[Feature #14912]</a> Introduce pattern matching syntax (greggzst)<br>
Many modern languages have introduced pattern matching. I used it in scala and found it very easy to utilize and understand especially in recursion. It makes extracting data easier as well.</p> Ruby master - Misc #15129: DevelopersMeeting20181010Japanhttps://redmine.ruby-lang.org/issues/15129?journal_id=742332018-09-28T18:04:30Zzverok (Victor Shepelev)zverok.offline@gmail.com
<ul></ul><ul>
<li>[Feature <a class="issue tracker-2 status-5 priority-4 priority-default closed" title="Feature: Enumerator#chain (Closed)" href="https://redmine.ruby-lang.org/issues/15144">#15144</a>] <code>Enumerator#chain</code>
</li>
</ul> Ruby master - Misc #15129: DevelopersMeeting20181010Japanhttps://redmine.ruby-lang.org/issues/15129?journal_id=742712018-10-02T07:13:42Zduerst (Martin Dürst)duerst@it.aoyama.ac.jp
<ul></ul><ul>
<li>[Feature <a class="issue tracker-2 status-5 priority-4 priority-default closed" title="Feature: How to deal with capitalizing Georgian in Unicode 11.0.0 (Closed)" href="https://redmine.ruby-lang.org/issues/14839">#14839</a>] How to deal with capitalizing Georgian in Unicode 11.0.0<br>
I need feedback on this to be able to implement in in time for the Ruby 2.6 release.</li>
</ul> Ruby master - Misc #15129: DevelopersMeeting20181010Japanhttps://redmine.ruby-lang.org/issues/15129?journal_id=742892018-10-03T05:59:18Zduerst (Martin Dürst)duerst@it.aoyama.ac.jp
<ul></ul><ul>
<li>[Feature 15195] How to deal with new Japanese era
<ul>
<li>We should prepare early (even if it's just to check that we need to do nothing)</li>
</ul>
</li>
</ul> Ruby master - Misc #15129: DevelopersMeeting20181010Japanhttps://redmine.ruby-lang.org/issues/15129?journal_id=743402018-10-08T07:09:16Zzverok (Victor Shepelev)zverok.offline@gmail.com
<ul></ul><p>I am not sure if it is appropriate, but I'd also be very glad to hear about some "stale" discussions. They were typically reacted on developer meetings as "in general, good proposal (but not sure when it would be implemented/not sure about the name)", or something like that, and I'd like to know maybe we should do something to push them further? List of tickets:</p>
<ul>
<li>[Feature <a class="issue tracker-2 status-5 priority-4 priority-default closed" title="Feature: Startless range (Closed)" href="https://redmine.ruby-lang.org/issues/14799">#14799</a>] Startless range: usefulness discussed, patch provided by <a class="user active user-mention" href="https://redmine.ruby-lang.org/users/18">@mame (Yusuke Endoh)</a>, waits for Matz's decision (?)</li>
<li>[Feature <a class="issue tracker-2 status-5 priority-4 priority-default closed" title="Feature: Comparable#clamp with a range (Closed)" href="https://redmine.ruby-lang.org/issues/14784">#14784</a>] <code>Comparable#clamp</code> accepting range: comment for <a class="user active user-mention" href="https://redmine.ruby-lang.org/users/271">@akr (Akira Tanaka)</a> about "needlessly big" proposal, I answered it, is it makes the proposal more likely to be accepted?</li>
<li>[Feature <a class="issue tracker-2 status-5 priority-4 priority-default closed" title="Feature: Add composition for procs (Closed)" href="https://redmine.ruby-lang.org/issues/6284">#6284</a>] Composition for procs: the last thing Matz has said is the operators are chosen (<code><<</code> and <code>>></code>), and "We need more discussion if we would add combination methods to the <code>Symbol</code> class." Is there a chance proc composition would make it way in the 2.6?</li>
<li>[Feature <a class="issue tracker-2 status-5 priority-4 priority-default closed" title="Feature: Syntax sugar for method reference (Closed)" href="https://redmine.ruby-lang.org/issues/13581">#13581</a>] Syntax sugar for method reference. The last thing Matz have said is: "<code>.:</code> looks best to me (followed by <code>:::</code>). Let me consider it for a while." Are there any choices made? Could we expect this for 2.6?</li>
<li>[Feature <a class="issue tracker-2 status-5 priority-4 priority-default closed" title="Feature: Enumerator.generate (Closed)" href="https://redmine.ruby-lang.org/issues/14781">#14781</a>] <code>Enumerator#generate</code> It seems like people feel cautious enthusiasm about it, but not sure about the name. What should be done here? Voting on the name? Providing the patch with <em>some</em> name, and then voting for the name?</li>
</ul> Ruby master - Misc #15129: DevelopersMeeting20181010Japanhttps://redmine.ruby-lang.org/issues/15129?journal_id=743422018-10-08T10:33:49Zduerst (Martin Dürst)duerst@it.aoyama.ac.jp
<ul></ul><ul>
<li>How to address increasing spam to the bug tracker. #15212/#15213 are just two examples. They get removed (return a 404), which is good. But they reach the mailing list and its subscribers, which is a problem. Prefiltering bugs with URIs in titles seems to be a good start.</li>
</ul> Ruby master - Misc #15129: DevelopersMeeting20181010Japanhttps://redmine.ruby-lang.org/issues/15129?journal_id=743732018-10-10T02:00:34Zshyouhei (Shyouhei Urabe)shyouhei@ruby-lang.org
<ul><li><strong>Description</strong> updated (<a title="View differences" href="/journals/74373/diff?detail_id=50045">diff</a>)</li></ul> Ruby master - Misc #15129: DevelopersMeeting20181010Japanhttps://redmine.ruby-lang.org/issues/15129?journal_id=743742018-10-10T05:09:34Zhsbt (Hiroshi SHIBATA)hsbt@ruby-lang.org
<ul><li><strong>Description</strong> updated (<a title="View differences" href="/journals/74374/diff?detail_id=50046">diff</a>)</li></ul> Ruby master - Misc #15129: DevelopersMeeting20181010Japanhttps://redmine.ruby-lang.org/issues/15129?journal_id=743872018-10-10T07:03:57Ztarui (Masaya Tarui)tarui@prx.jp
<ul><li><strong>Description</strong> updated (<a title="View differences" href="/journals/74387/diff?detail_id=50055">diff</a>)</li></ul> Ruby master - Misc #15129: DevelopersMeeting20181010Japanhttps://redmine.ruby-lang.org/issues/15129?journal_id=744842018-10-17T09:40:33Zduerst (Martin Dürst)duerst@it.aoyama.ac.jp
<ul><li><strong>Subject</strong> changed from <i>DevelopersMeeting201801010Japan</i> to <i>DevelopersMeeting20181010Japan</i></li></ul> Ruby master - Misc #15129: DevelopersMeeting20181010Japanhttps://redmine.ruby-lang.org/issues/15129?journal_id=748552018-11-14T04:34:38Zhsbt (Hiroshi SHIBATA)hsbt@ruby-lang.org
<ul><li><strong>Status</strong> changed from <i>Open</i> to <i>Closed</i></li></ul>