https://bugs.ruby-lang.org/https://bugs.ruby-lang.org/favicon.ico?17113305112021-03-20T02:51:51ZRuby Issue Tracking SystemRuby master - Misc #17734: DevelopersMeeting20210416Japanhttps://bugs.ruby-lang.org/issues/17734?journal_id=910002021-03-20T02:51: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 #17734: DevelopersMeeting20210416Japanhttps://bugs.ruby-lang.org/issues/17734?journal_id=912692021-04-02T22:13:33Zjeremyevans0 (Jeremy Evans)merch-redmine@jeremyevans.net
<ul></ul><ul>
<li>[Bug <a class="issue tracker-2 status-5 priority-4 priority-default closed" title="Feature: SyntaxError in endless method (Closed)" href="https://bugs.ruby-lang.org/issues/17398">#17398</a>] SyntaxError in endless method (jeremyevans0)
<ul>
<li>I don't believe this is a bug, but maybe it is a useful feature.</li>
<li><a class="user active user-mention" href="https://bugs.ruby-lang.org/users/18">@mame (Yusuke Endoh)</a> has a patch that allows commands as the RHS of a endless method.</li>
<li>However, @mame's patch doesn't allow direct usage with method visibility methods such as private.</li>
<li>Do we want to support this syntax, or can this be closed (or moved to Feature)?</li>
</ul>
</li>
<li>[Bug <a class="issue tracker-2 status-5 priority-4 priority-default closed" title="Feature: Remove Fixnum and Bignum (Closed)" href="https://bugs.ruby-lang.org/issues/17403">#17403</a>] Remove Fixnum and Bignum (jeremyevans0)
<ul>
<li>Do we want to remove Fixnum and Bignum in Ruby 3.1?</li>
<li>If not, can we decide on a later version where they can be removed, such as 3.2 or 4.0?</li>
</ul>
</li>
<li>[Bug <a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Bug: RubyVM::AbstractSyntaxTree.of(method) returns meaningless node if the method is defined in eval (Closed)" href="https://bugs.ruby-lang.org/issues/16983">#16983</a>] RubyVM::AbstractSyntaxTree.of(method) returns meaningless node if the method is defined in eval (jeremyevans0)
<ul>
<li>
<code>RubyVM::AbstractSyntaxTree.of(method)</code> relies on reading the file with the method source, which could have changed or could not exist at all.</li>
<li>I don't think we can work around that without keeping the abstract syntax tree or source code of all methods in memory, which seems wasteful.</li>
<li>Is the current behavior a bug, or should we just accept the current behavior as spec and close this?</li>
</ul>
</li>
<li>[Bug <a class="issue tracker-1 status-6 priority-4 priority-default closed" title="Bug: Delegator does not delegate protected methods (Rejected)" href="https://bugs.ruby-lang.org/issues/9542">#9542</a>] Delegator does not delegate protected methods (jeremyevans0)
<ul>
<li>Do we want to add a way to tell if a method was called with an implicit receiver or self?</li>
<li>We may be able to implement this via a VM frame flag and a method to check it.</li>
<li>If we don't want to add such a way, can we accept the current behavior as spec and close this?</li>
</ul>
</li>
<li>[Bug <a class="issue tracker-1 status-6 priority-4 priority-default closed" title="Bug: Should rb_struct_s_members() be public API? (Rejected)" href="https://bugs.ruby-lang.org/issues/11230">#11230</a>] Should rb_struct_s_members() be public API? (jeremyevans0)
<ul>
<li>This is still public in the C-API.</li>
<li>Do we want to keep it and close this issue, or do we want to remove it?</li>
<li>If we want to remove it, how should it be deprecated?</li>
</ul>
</li>
</ul> Ruby master - Misc #17734: DevelopersMeeting20210416Japanhttps://bugs.ruby-lang.org/issues/17734?journal_id=912702021-04-02T23:57:18Ztenderlovemaking (Aaron Patterson)tenderlove@ruby-lang.org
<ul></ul><ul>
<li>[Feature <a class="issue tracker-2 status-1 priority-4 priority-default" title="Feature: Const source location without name (Open)" href="https://bugs.ruby-lang.org/issues/17749">#17749</a>] Add <code>Module#source_location</code>
<ul>
<li>It's similar to the const_source_location feature, but easier to use when you don't know the constant name, or enclosing const</li>
<li>This is useful for debugging</li>
</ul>
</li>
<li>[Feature <a class="issue tracker-2 status-1 priority-4 priority-default" title="Feature: Add Module#namespace (Open)" href="https://bugs.ruby-lang.org/issues/17753">#17753</a>] Add <code>Module#namespace</code>
<ul>
<li>
<code>A::B.namespace</code> will return <code>A</code>
</li>
<li>This is to help with finding "sibling" constants of <code>B</code> so we don't have to parse the constant name</li>
<li>This is also useful for debugging</li>
</ul>
</li>
</ul> Ruby master - Misc #17734: DevelopersMeeting20210416Japanhttps://bugs.ruby-lang.org/issues/17734?journal_id=913502021-04-07T06:33:46Zmame (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: A simple way to trace object allocation (Closed)" href="https://bugs.ruby-lang.org/issues/17762">#17762</a>] A simple way to trace object allocation
<ul>
<li>I want <code>require "objspace/trace"</code> or something which is a very useful debugging tool to identify the allocation site of an object.</li>
</ul>
</li>
</ul> Ruby master - Misc #17734: DevelopersMeeting20210416Japanhttps://bugs.ruby-lang.org/issues/17734?journal_id=913552021-04-07T16:24:08ZDan0042 (Daniel DeLorme)
<ul></ul><ul>
<li>[Feature <a class="issue tracker-2 status-1 priority-4 priority-default" title="Feature: String#casecmp performance improvement (Open)" href="https://bugs.ruby-lang.org/issues/17682">#17682</a>] String#casecmp performance improvement (dan0042)
<ul>
<li>Is it ok to make casecmp faster?</li>
</ul>
</li>
</ul> Ruby master - Misc #17734: DevelopersMeeting20210416Japanhttps://bugs.ruby-lang.org/issues/17734?journal_id=913872021-04-08T12:35:21Zmarcandre (Marc-Andre Lafortune)marcandre-ruby-core@marc-andre.ca
<ul></ul><ul>
<li>[Feature <a class="issue tracker-2 status-5 priority-4 priority-default closed" title="Feature: Array#intersect? (Closed)" href="https://bugs.ruby-lang.org/issues/15198">#15198</a>] Add Array#intersect? (marcandre)
<ul>
<li>Ok to add?</li>
</ul>
</li>
</ul> Ruby master - Misc #17734: DevelopersMeeting20210416Japanhttps://bugs.ruby-lang.org/issues/17734?journal_id=913892021-04-08T13:05:06Zbyroot (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: Around `Process.fork` callbacks API (Closed)" href="https://bugs.ruby-lang.org/issues/17795">#17795</a>] <code>before_fork</code> and <code>after_fork</code> callback API
<ul>
<li>Many libraries out there use various tricks to detect the process being forked, most commonly <code>Process.pid != @pid</code>, but <code>glibc</code> no longer cache the PID so these libraries end up doing syscalls in tight loops.</li>
<li>If a callback API is too complicated, I proposed a simplee alternative that is to have <code>Kernel.fork</code> be a simple delegator to <code>Process.fork</code> <a href="https://github.com/ruby/ruby/pull/4361" class="external">https://github.com/ruby/ruby/pull/4361</a>, This would makes it easy for libraries to decorate fork to have their own callbacks on either before or after fork.</li>
</ul>
</li>
</ul> Ruby master - Misc #17734: DevelopersMeeting20210416Japanhttps://bugs.ruby-lang.org/issues/17734?journal_id=915242021-04-13T15:07:59Zparker (Parker Finch)
<ul></ul><ul>
<li>[Feature <a class="issue tracker-2 status-1 priority-4 priority-default" title="Feature: Enumerable#accumulate (Open)" href="https://bugs.ruby-lang.org/issues/17016">#17016</a>] Add <code>Enumerable#accumulate</code> (parkerfinch)
<ul>
<li>Is the name <code>#accumulate</code> acceptable?</li>
<li>Is this feature ok to add?</li>
</ul>
</li>
</ul> Ruby master - Misc #17734: DevelopersMeeting20210416Japanhttps://bugs.ruby-lang.org/issues/17734?journal_id=915942021-04-17T08:18:04Zmame (Yusuke Endoh)mame@ruby-lang.org
<ul><li><strong>Description</strong> updated (<a title="View differences" href="/journals/91594/diff?detail_id=59800">diff</a>)</li><li><strong>Status</strong> changed from <i>Open</i> to <i>Closed</i></li></ul>