https://bugs.ruby-lang.org/https://bugs.ruby-lang.org/favicon.ico?17113305112021-09-16T15:26:17ZRuby Issue Tracking SystemRuby master - Misc #18174: DevelopersMeeting20211021Japanhttps://bugs.ruby-lang.org/issues/18174?journal_id=937232021-09-16T15:26:17Zmame (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 #18174: DevelopersMeeting20211021Japanhttps://bugs.ruby-lang.org/issues/18174?journal_id=937382021-09-17T08:07:17Zmame (Yusuke Endoh)mame@ruby-lang.org
<ul></ul><ul>
<li>[Feature <a class="issue tracker-2 status-5 priority-4 priority-default closed" title="Feature: Make Coverage suspendable (Closed)" href="https://bugs.ruby-lang.org/issues/18176">#18176</a>] Make Coverage suspendable (mame)
<ul>
<li>I'd like to add <code>Coverage.suspend</code> and <code>Coverage.resume</code>. Any opinion?</li>
</ul>
</li>
<li>[Bug <a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Bug: Exception#inspect should not include newlines (Closed)" href="https://bugs.ruby-lang.org/issues/18170">#18170</a>] <code>Exception#inspect</code> should not include newlines (mame)
<ul>
<li>I've created a PR for <code>StandardError.new("foo\nbar") #=> #<StandardError: "foo\nbar"></code>. I had to modify some tests. Is it acceptable?</li>
</ul>
</li>
</ul> Ruby master - Misc #18174: DevelopersMeeting20211021Japanhttps://bugs.ruby-lang.org/issues/18174?journal_id=938832021-09-27T04:04:35Zioquatix (Samuel Williams)samuel@oriontransfer.net
<ul></ul><ul>
<li>[Feature <a class="issue tracker-2 status-1 priority-4 priority-default" title="Feature: Introduce general model/semantic for immutability. (Open)" href="https://bugs.ruby-lang.org/issues/18035">#18035</a>] Introduce general model/semantic for immutable by default.
<ul>
<li>Can we agree on interface and implementation.</li>
<li>
<code>Process::Status</code> is example use-case. Should be many more.</li>
</ul>
</li>
<li>[Feature <a class="issue tracker-2 status-1 priority-4 priority-default" title="Feature: Capture error in ensure block. (Open)" href="https://bugs.ruby-lang.org/issues/18083">#18083</a>] Capture error in ensure block.
<ul>
<li>Can we deprecate <code>$!</code> (& <code>$@</code>)? It's dangerous and every use case is better with explicit capture. Also may have some performance advantages.</li>
</ul>
</li>
<li>[Feature <a class="issue tracker-2 status-5 priority-4 priority-default closed" title="Feature: Introduce `IO::Buffer` for fiber scheduler. (Closed)" href="https://bugs.ruby-lang.org/issues/18020">#18020</a>] Introduce <code>IO::Buffer</code> for fiber scheduler.
<ul>
<li>For efficient file IO we need an internal buffer with well defined semantics suitable for IO.</li>
</ul>
</li>
<li>[Feature <a class="issue tracker-2 status-5 priority-4 priority-default closed" title="Feature: Introduce non-blocking `Process.wait`, `Kernel.system` and related methods. (Closed)" href="https://bugs.ruby-lang.org/issues/17369">#17369</a>] Introduce non-blocking <code>Process.wait</code>, <code>Kernel.system</code> and related methods.
<ul>
<li>Currently, <code>$?</code> is thread-local, but it should be fiber local.</li>
<li>Should we try to fix <code>$?</code> or deprecate it?</li>
<li>Introduce new interface? <code>system(...) {|status| ...}</code>?</li>
</ul>
</li>
<li>[Bug <a class="issue tracker-2 status-5 priority-4 priority-default closed" title="Feature: No easy way to format exception messages per thread/fiber scheduler context. (Closed)" href="https://bugs.ruby-lang.org/issues/18194">#18194</a>] No easy way to format exception messages per thread/fiber scheduler context.
<ul>
<li>Can we come to an agreement on what this looks like for Ruby 3.1?</li>
<li>Can we introduce fiber scheduler hook for unhandled exceptions?</li>
</ul>
</li>
</ul> Ruby master - Misc #18174: DevelopersMeeting20211021Japanhttps://bugs.ruby-lang.org/issues/18174?journal_id=939262021-09-28T23:26:09Zshugo (Shugo Maeda)
<ul></ul><ul>
<li>[Bug <a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Bug: Prohibit include/prepend in refinement modules (Closed)" href="https://bugs.ruby-lang.org/issues/17429">#17429</a>] Prohibit include/prepend in refinement modules
<ul>
<li>Is the name <code>Refinement#import</code> OK?</li>
</ul>
</li>
</ul> Ruby master - Misc #18174: DevelopersMeeting20211021Japanhttps://bugs.ruby-lang.org/issues/18174?journal_id=940122021-10-04T23:52:28Zduerst (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: Variable Width Allocation: Strings (Closed)" href="https://bugs.ruby-lang.org/issues/18239">#18239</a>] Variable Width Allocation: Strings
<ul>
<li>Discuss deployment schedule and binary incompatibility issues.</li>
</ul>
</li>
</ul> Ruby master - Misc #18174: DevelopersMeeting20211021Japanhttps://bugs.ruby-lang.org/issues/18174?journal_id=941032021-10-09T07:58:35Znobu (Nobuyoshi Nakada)nobu@ruby-lang.org
<ul></ul><ul>
<li>[Feature <a class="issue tracker-2 status-1 priority-4 priority-default" title="Feature: Parser makes multiple assignment sad in confusing way (Open)" href="https://bugs.ruby-lang.org/issues/18242">#18242</a>] Allow multiple assignment in logical expression
<ul>
<li>
<code>1 < 2 and a, b = 2, 1</code> and so on.</li>
</ul>
</li>
</ul> Ruby master - Misc #18174: DevelopersMeeting20211021Japanhttps://bugs.ruby-lang.org/issues/18174?journal_id=941082021-10-11T21:57:51Zjeremyevans0 (Jeremy Evans)merch-redmine@jeremyevans.net
<ul></ul><ul>
<li>[Misc <a class="issue tracker-5 status-1 priority-4 priority-default" title="Misc: Add Feature Triaging Guide (Open)" href="https://bugs.ruby-lang.org/issues/18248">#18248</a>] Add Feature Triaging Guide (jeremyevans0)
<ul>
<li>Is it OK to add a feature triaging guide and start using it triage feature requests?</li>
</ul>
</li>
<li>[Bug <a class="issue tracker-1 status-6 priority-4 priority-default closed" title="Bug: Load did_you_mean/error_highlight even with --disable-gems (Rejected)" href="https://bugs.ruby-lang.org/issues/18066">#18066</a>] Load did_you_mean/error_highlight even with --disable-gems (jeremyevans0)
<ul>
<li>Should --disable-gems also disable did_you_mean and error_highlight?</li>
<li>Most developers appear in favor, though <a class="user active user-mention" href="https://bugs.ruby-lang.org/users/18">@mame (Yusuke Endoh)</a> is against (but not strongly opposed).</li>
</ul>
</li>
<li>[Bug <a class="issue tracker-1 status-6 priority-4 priority-default closed" title="Bug: Float#clamp() returns ArgumentError (comparison of Float with 1 failed) (Rejected)" href="https://bugs.ruby-lang.org/issues/18187">#18187</a>] <code>Float#clamp()</code> returns <code>ArgumentError</code> (comparison of Float with 1 failed) (jeremyevans0)
<ul>
<li>How should <code>Float#clamp</code> handle case where receiver is NaN?</li>
<li>Currently it raises <code>ArgumentError</code>, but that is due to implementation details, not by design.</li>
<li>Is it OK to change it to return the receiver (NaN) in this case?</li>
</ul>
</li>
<li>[Bug <a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Bug: newline argument of File.open seems not respected on Windows (Closed)" href="https://bugs.ruby-lang.org/issues/12436">#12436</a>] newline argument of <code>File.open</code> seems not respected on Windows (jeremyevans0)
<ul>
<li>The option is currently ignored due to an oversight when the code was originally added.</li>
<li>Is it OK to introduce <code>lf_newline</code> transcoder and <code>newline: :lf</code> option to fix this?</li>
<li>Also, is <code>newline: :crlf</code> supposed to convert <code>\r\n</code> to <code>\n</code> during read only on Windows?</li>
</ul>
</li>
</ul> Ruby master - Misc #18174: DevelopersMeeting20211021Japanhttps://bugs.ruby-lang.org/issues/18174?journal_id=941242021-10-14T14:35:49Zbyroot (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 GC.stat[:total_time] when GC profiling enabled (Closed)" href="https://bugs.ruby-lang.org/issues/10917">#10917</a>] Add <code>GC.stat[:total_time]</code> when GC profiling enabled
<ul>
<li><a class="user active user-mention" href="https://bugs.ruby-lang.org/users/17">@ko1 (Koichi Sasada)</a> did submit a pull request which seem fine except maybe for 32bits support.</li>
<li><a class="user active user-mention" href="https://bugs.ruby-lang.org/users/17">@ko1 (Koichi Sasada)</a> did also measure the overhead and it appeared small.</li>
<li>Could this feature be merged for Ruby 3.1?</li>
</ul>
</li>
</ul> Ruby master - Misc #18174: DevelopersMeeting20211021Japanhttps://bugs.ruby-lang.org/issues/18174?journal_id=941332021-10-15T11:09:26Zbyroot (Jean Boussier)byroot@ruby-lang.org
<ul></ul><ul>
<li>[Feature <a class="issue tracker-2 status-8 priority-4 priority-default closed" title="Feature: Where we should install a header file when `gem install --user`? (Third Party's Issue)" href="https://bugs.ruby-lang.org/issues/17760">#17760</a>] Where we should install a header file when <code>gem install --user</code>?
<ul>
<li>
<code>digest</code> have been gemified. However its <code>extconf.rb</code> have <code>$INSTALLFILES = { "digest.h" => "$(HDRDIR)" }</code> which fail for most people because ruby's <code>include</code> directory is owned by root.</li>
<li>What should rubygems do here? Have a secondary user owned <code>include</code> directory?</li>
<li>If I have several versions of <code>digest</code> installed? How gems linking against it would know which version to use?</li>
<li>If there's no clear solution, with 3.1.0 approaching, should we revert that <code>digest</code> gemification so that 3.1.0 is actually usable?</li>
</ul>
</li>
</ul> Ruby master - Misc #18174: DevelopersMeeting20211021Japanhttps://bugs.ruby-lang.org/issues/18174?journal_id=941582021-10-18T03:21:51Znobu (Nobuyoshi Nakada)nobu@ruby-lang.org
<ul><li><strong>Description</strong> updated (<a title="View differences" href="/journals/94158/diff?detail_id=61003">diff</a>)</li></ul> Ruby master - Misc #18174: DevelopersMeeting20211021Japanhttps://bugs.ruby-lang.org/issues/18174?journal_id=941722021-10-19T09:28:05ZEregon (Benoit Daloze)
<ul></ul><ul>
<li>[Feature <a class="issue tracker-2 status-1 priority-4 priority-default" title="Feature: Change the canonical name of Thread::Mutex, Thread::Queue, Thread::SizedQueue and Thread::Conditi... (Open)" href="https://bugs.ruby-lang.org/issues/18256">#18256</a>] Change the canonical name of Thread::Mutex, Thread::Queue, Thread::SizedQueue and Thread::ConditionVariable to just Mutex, Queue, SizedQueue and ConditionVariable (eregon)
<ul>
<li>OK? (sorry for late addition for the meeting, we can move to next meeting if needed, but would be best to decide sooner than later)</li>
</ul>
</li>
</ul> Ruby master - Misc #18174: DevelopersMeeting20211021Japanhttps://bugs.ruby-lang.org/issues/18174?journal_id=941872021-10-20T01:28:04ZDan0042 (Daniel DeLorme)
<ul></ul><ul>
<li>[Feature <a class="issue tracker-2 status-5 priority-4 priority-default closed" title="Feature: Around `Process.fork` callbacks API (Closed)" href="https://bugs.ruby-lang.org/issues/17795">#17795</a>] Around <code>Process.fork</code> callbacks API (dan0042)
<ul>
<li>A few naming suggestions have been made; does Matz like any of them?</li>
</ul>
</li>
<li>[Feature <a class="issue tracker-2 status-5 priority-4 priority-default closed" title="Feature: Add support for Regexp timeouts (Closed)" href="https://bugs.ruby-lang.org/issues/17837">#17837</a>] Add support for Regexp timeouts (dan0042)
<ul>
<li>Adding this to ruby 3.1 with a safe (high) value for <code>Regexp.backtrack_limit</code> would be an improvement on the current lack of limit, and would allow to get measurements from real-world applications for a better default value.</li>
</ul>
</li>
</ul> Ruby master - Misc #18174: DevelopersMeeting20211021Japanhttps://bugs.ruby-lang.org/issues/18174?journal_id=941902021-10-20T08:25:11Zbyroot (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 an `offset` parameter to String#unpack and String#unpack1 (Closed)" href="https://bugs.ruby-lang.org/issues/18254">#18254</a>] Add an <code>offset</code> parameter to <code>String#unpack</code> and <code>String#unpack1</code>
<ul>
<li>Binary protocol parsers currently have to slice their buffer repeatedly, this new argument would save a lot of string copying.</li>
</ul>
</li>
</ul> Ruby master - Misc #18174: DevelopersMeeting20211021Japanhttps://bugs.ruby-lang.org/issues/18174?journal_id=941952021-10-20T14:25:09ZEregon (Benoit Daloze)
<ul></ul><ul>
<li>[Bug <a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Bug: Queue operations are allowed after it is frozen (Closed)" href="https://bugs.ruby-lang.org/issues/17146">#17146</a>] Queue operations are allowed after it is frozen. (eregon)
<ul>
<li>This is an obvious inconsistency and it makes no sense whenever we discuss deep freezing object graphs. Let's fix it.</li>
</ul>
</li>
</ul> Ruby master - Misc #18174: DevelopersMeeting20211021Japanhttps://bugs.ruby-lang.org/issues/18174?journal_id=942292021-10-21T11:37:18Zmame (Yusuke Endoh)mame@ruby-lang.org
<ul></ul><p>We held the dev-meeting but didn't finish until the last topic. An extra meeting will be held at the next Monday.</p> Ruby master - Misc #18174: DevelopersMeeting20211021Japanhttps://bugs.ruby-lang.org/issues/18174?journal_id=942952021-10-25T09:11:28Zmame (Yusuke Endoh)mame@ruby-lang.org
<ul><li><strong>Description</strong> updated (<a title="View differences" href="/journals/94295/diff?detail_id=61047">diff</a>)</li><li><strong>Status</strong> changed from <i>Open</i> to <i>Closed</i></li></ul>