https://bugs.ruby-lang.org/https://bugs.ruby-lang.org/favicon.ico?17113305112019-07-11T12:37:14ZRuby Issue Tracking SystemRuby master - Misc #15996: DevelopersMeeting20190829Japanhttps://bugs.ruby-lang.org/issues/15996?journal_id=792972019-07-11T12:37:14Zmame (Yusuke Endoh)mame@ruby-lang.org
<ul></ul><p>I added the following note.</p>
<pre><code>**A short summary of a ticket is strongly recommended. We cannot read all discussion of the ticket in a limited time.**
A proposal is often changed during the discussion, so it is very helpful to summarize the latest/current proposal, post it as a comment in the ticket, and write a link to the comment.
</code></pre>
<p>Please consider adding a short summary comment to the ticket you want us to discuss.</p> Ruby master - Misc #15996: DevelopersMeeting20190829Japanhttps://bugs.ruby-lang.org/issues/15996?journal_id=792982019-07-11T12:39:01Zmame (Yusuke Endoh)mame@ruby-lang.org
<ul></ul><p>Carry over.</p>
<ul>
<li>[Feature <a class="issue tracker-2 status-5 priority-4 priority-default closed" title="Feature: Unhelpful error message when naming a module with the same name as an existing class (Closed)" href="https://bugs.ruby-lang.org/issues/11460">#11460</a>] Unhelpful error message when naming a module with the same name as an existing class (nobu)</li>
<li>[Misc <a class="issue tracker-2 status-5 priority-4 priority-default closed" title="Feature: Let memory sizes of the various IMEMO object types be reflected correctly (Closed)" href="https://bugs.ruby-lang.org/issues/15805">#15805</a>] Let memory sizes of the various IMEMO object types be reflected correctly (methodmissing)
<ul>
<li>Only the imemo_tmpbuf type's auxiliary malloc heap buffer is factored into obj_memsize_of, other imemo types also alloc on the heap</li>
<li>PR: <a href="https://github.com/ruby/ruby/pull/2140" class="external">https://github.com/ruby/ruby/pull/2140</a>
</li>
</ul>
</li>
<li>[Misc <a class="issue tracker-5 status-2 priority-4 priority-default" title="Misc: Explicitly initialise encodings on init to remove branches on encoding lookup (Assigned)" href="https://bugs.ruby-lang.org/issues/15806">#15806</a>] Explicitly initialise encodings on init to remove branches on encoding lookup (methodmissing)
<ul>
<li>Currently rb_enc_from_index and related methods explicitly check for encoding table init on each call - I think this should be initialised at boot time instead as even the simple case of loading the interpreter requires the encoding table to be loaded anyways (symbol.c)</li>
<li>PR: <a href="https://github.com/ruby/ruby/pull/2128" class="external">https://github.com/ruby/ruby/pull/2128</a>
</li>
</ul>
</li>
</ul> Ruby master - Misc #15996: DevelopersMeeting20190829Japanhttps://bugs.ruby-lang.org/issues/15996?journal_id=793002019-07-11T12:39:25Zmame (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 #15996: DevelopersMeeting20190829Japanhttps://bugs.ruby-lang.org/issues/15996?journal_id=798502019-07-23T13:24:15Znobu (Nobuyoshi Nakada)nobu@ruby-lang.org
<ul></ul><ul>
<li>[Feature <a class="issue tracker-2 status-6 priority-4 priority-default closed" title="Feature: Eval InstructionSequence with binding (Rejected)" href="https://bugs.ruby-lang.org/issues/12093">#12093</a>] Eval InstructionSequence with binding</li>
</ul> Ruby master - Misc #15996: DevelopersMeeting20190829Japanhttps://bugs.ruby-lang.org/issues/15996?journal_id=799062019-07-23T18:10:58Zjeremyevans0 (Jeremy Evans)merch-redmine@jeremyevans.net
<ul></ul><ul>
<li>[Bug <a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Bug: Defining a writer as a Struct member allowed? (Closed)" href="https://bugs.ruby-lang.org/issues/11326">#11326</a>] Defining a writer as a Struct member allowed?
<ul>
<li>Should we ban struct members ending in <code>=</code>?</li>
<li>Do we also want to ban struct members ending in <code>!</code> or <code>?</code>?</li>
</ul>
</li>
</ul> Ruby master - Misc #15996: DevelopersMeeting20190829Japanhttps://bugs.ruby-lang.org/issues/15996?journal_id=801902019-07-29T10:36:13ZGlass_saga (Masaki Matsushita)glass.saga@gmail.com
<ul></ul><ul>
<li>[Feature <a class="issue tracker-2 status-1 priority-4 priority-default" title="Feature: String#each_chunk and #chunks (Open)" href="https://bugs.ruby-lang.org/issues/15588">#15588</a>] String#each_chunk and #chunks
<ul>
<li>name: #each_slice and #slices are better?</li>
<li>size as characters or bytes</li>
<li>should we support :strip parameter?</li>
</ul>
</li>
<li>[Feature <a class="issue tracker-2 status-5 priority-4 priority-default closed" title="Feature: Addrinfo.getaddrinfo supports timeout (Closed)" href="https://bugs.ruby-lang.org/issues/15553">#15553</a>] Addrinfo.getaddrinfo supports timeout
<ul>
<li>I'd like to have some feedback for patch2.diff</li>
</ul>
</li>
</ul> Ruby master - Misc #15996: DevelopersMeeting20190829Japanhttps://bugs.ruby-lang.org/issues/15996?journal_id=802472019-07-30T04:32:37Zsikachu (Prem Sichanugrist)s+ruby@sikac.hu
<ul></ul><ul>
<li>[Misc <a class="issue tracker-5 status-7 priority-4 priority-default closed" title="Misc: Reconsider numbered parameters (Feedback)" href="https://bugs.ruby-lang.org/issues/15723">#15723</a>] Reconsider numbered parameters
<ul>
<li>Reading from description, I think there are a few supporters of removing <code>@1</code>, <code>@2</code> in favor of just having <code>@</code> refer to the first argument.</li>
<li>I also believe having just <code>@</code> is enough for major use cases, and for the readability of the code when multiple implicit receivers are used.</li>
<li>Proposal: Remove <code>@1</code> and <code>@2</code> and have only <code>@</code> for the first argument in Ruby 2.7+</li>
</ul>
</li>
</ul> Ruby master - Misc #15996: DevelopersMeeting20190829Japanhttps://bugs.ruby-lang.org/issues/15996?journal_id=802712019-07-30T08:42:52Zko1 (Koichi Sasada)
<ul></ul><p>Triage:</p>
<ul>
<li>[Feature <a class="issue tracker-2 status-5 priority-4 priority-default closed" title="Feature: Allow String#-@ to deduplicate tainted string, but return an untainted one (Closed)" href="https://bugs.ruby-lang.org/issues/15998">#15998</a>] Allow String#-@ to deduplicate tainted string, but return an untainted one
<ul>
<li>taint removal schedule</li>
</ul>
</li>
<li>[Feature <a class="issue tracker-2 status-7 priority-4 priority-default closed" title="Feature: Enumerable#compact proposal (Feedback)" href="https://bugs.ruby-lang.org/issues/15123">#15123</a>] Enumerable#compact proposal</li>
<li>[Feature <a class="issue tracker-2 status-1 priority-4 priority-default" title="Feature: Tracing instance variable assignment (Open)" href="https://bugs.ruby-lang.org/issues/15854">#15854</a>] Tracing instance variable assignment</li>
<li>[Bug <a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Bug: program name variables tainted (Closed)" href="https://bugs.ruby-lang.org/issues/9588">#9588</a>] program name variables tainted</li>
<li>[Feature <a class="issue tracker-2 status-1 priority-4 priority-default" title="Feature: Add BLAKE2 support to Digest (Open)" href="https://bugs.ruby-lang.org/issues/12802">#12802</a>] Add BLAKE2 support to Digest</li>
<li>[Feature <a class="issue tracker-2 status-1 priority-4 priority-default" title="Feature: Provide an alias to Kernel#caller_locations(1,1) and Kernel#caller(1,1) (Open)" href="https://bugs.ruby-lang.org/issues/16001">#16001</a>] Provide an alias to Kernel#caller_locations(1,1) and Kernel#caller(1,1)</li>
<li>[Bug <a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Bug: Inherited Array class missing (Closed)" href="https://bugs.ruby-lang.org/issues/7768">#7768</a>] Inherited Array class missing</li>
<li>[Bug <a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Bug: Process.clock_getres matches the clock in practice for Process::CLOCK_{PROCESS,THREAD}_CPUTIME_ID... (Closed)" href="https://bugs.ruby-lang.org/issues/16007">#16007</a>] Process.clock_getres matches the clock in practice for Process::CLOCK_{PROCESS,THREAD}_CPUTIME_ID FAILED fails on armv7hl</li>
<li>[Feature <a class="issue tracker-2 status-6 priority-4 priority-default closed" title="Feature: Add Array#pluck (Rejected)" href="https://bugs.ruby-lang.org/issues/15975">#15975</a>] Add Array#pluck</li>
<li>[Bug <a class="issue tracker-2 status-6 priority-4 priority-default closed" title="Feature: :~@ and :!@ are not parsed correctly (Rejected)" href="https://bugs.ruby-lang.org/issues/10463">#10463</a>] :~@ and :!@ are not parsed correctly</li>
<li>[Feature <a class="issue tracker-2 status-6 priority-4 priority-default closed" title="Feature: Named capture groups don't set local vars when matched using ~ (Rejected)" href="https://bugs.ruby-lang.org/issues/10123">#10123</a>] Named capture groups don't set local vars when matched using ~</li>
<li>[Feature <a class="issue tracker-2 status-6 priority-4 priority-default closed" title="Feature: Digit grouping (Rejected)" href="https://bugs.ruby-lang.org/issues/16011">#16011</a>] Digit grouping</li>
<li>[Feature <a class="issue tracker-2 status-1 priority-4 priority-default" title="Feature: Add a way to deprecate methods (Open)" href="https://bugs.ruby-lang.org/issues/16018">#16018</a>] Add a way to deprecate methods</li>
<li>[Bug <a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Bug: Date.new returns inconsistent errors when passed invalid arguments (Closed)" href="https://bugs.ruby-lang.org/issues/11935">#11935</a>] Date.new returns inconsistent errors when passed invalid arguments</li>
<li>[Bug <a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Bug: Wrong exception raised when IO.read from a pipe is passed an offset on Windows (Closed)" href="https://bugs.ruby-lang.org/issues/12230">#12230</a>] Wrong exception raised when IO.read from a pipe is passed an offset on Windows</li>
<li>[Bug <a class="issue tracker-1 status-6 priority-4 priority-default closed" title="Bug: Forbid `if` `elsif` without a condition (Rejected)" href="https://bugs.ruby-lang.org/issues/16020">#16020</a>] Forbid <code>if</code> <code>elsif</code> without a condition</li>
<li>[Bug <a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Bug: Method #extname return empty string if filename is dot ('.') (Closed)" href="https://bugs.ruby-lang.org/issues/15244">#15244</a>] Method #extname return empty string if filename is dot ('.')</li>
<li>[Feature <a class="issue tracker-2 status-5 priority-4 priority-default closed" title="Feature: UnboundMethod#apply (Closed)" href="https://bugs.ruby-lang.org/issues/15955">#15955</a>] UnboundMethod#apply</li>
<li>[Feature <a class="issue tracker-2 status-5 priority-4 priority-default closed" title="Feature: Add Array#overlap? for whether the intersection of 2 arrays is non empty? (Closed)" href="https://bugs.ruby-lang.org/issues/15976">#15976</a>] Add Array#overlap? for whether the intersection of 2 arrays is non empty?</li>
<li>[Bug <a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Bug: Should Exception#exception copy the backtrace? (Closed)" href="https://bugs.ruby-lang.org/issues/15558">#15558</a>] Should Exception#exception copy the backtrace?</li>
</ul>
<p>if there is a time to check...</p> Ruby master - Misc #15996: DevelopersMeeting20190829Japanhttps://bugs.ruby-lang.org/issues/15996?journal_id=802772019-07-30T11:30:00Znobu (Nobuyoshi Nakada)nobu@ruby-lang.org
<ul></ul><ul>
<li>[Feature <a class="issue tracker-2 status-5 priority-4 priority-default closed" title="Feature: Implement `File.absolute_path?` (Closed)" href="https://bugs.ruby-lang.org/issues/15868">#15868</a>] Implement <code>File.absolute_path?</code>
</li>
</ul> Ruby master - Misc #15996: DevelopersMeeting20190829Japanhttps://bugs.ruby-lang.org/issues/15996?journal_id=802952019-07-31T03:49:18Znobu (Nobuyoshi Nakada)nobu@ruby-lang.org
<ul></ul><ul>
<li>[Feature <a class="issue tracker-2 status-5 priority-4 priority-default closed" title="Feature: Expose fstring related APIs to C-extensions (Closed)" href="https://bugs.ruby-lang.org/issues/16029">#16029</a>] Expose fstring related APIs to C-extensions</li>
</ul> Ruby master - Misc #15996: DevelopersMeeting20190829Japanhttps://bugs.ruby-lang.org/issues/15996?journal_id=803002019-07-31T09:45:23ZEregon (Benoit Daloze)
<ul></ul><ul>
<li>[Feature <a class="issue tracker-2 status-1 priority-4 priority-default" title="Feature: Expose an API to pry-open the stack frames in Ruby (Open)" href="https://bugs.ruby-lang.org/issues/15778">#15778</a>] caller_locations(debug: true) to access bindings of the stack.
<ul>
<li>Can we introduce the API? If not, why not? If not, please propose a way to support such functionality on other Ruby implementations (e.g., JRuby, TruffleRuby).</li>
</ul>
</li>
</ul> Ruby master - Misc #15996: DevelopersMeeting20190829Japanhttps://bugs.ruby-lang.org/issues/15996?journal_id=803392019-08-02T00:08:30Znobu (Nobuyoshi Nakada)nobu@ruby-lang.org
<ul></ul><ul>
<li>[Feature <a class="issue tracker-2 status-5 priority-4 priority-default closed" title="Feature: Allow non-finalizable objects such as Integer, static Symbol etc in ObjectSpace::WeakMap (Closed)" href="https://bugs.ruby-lang.org/issues/16035">#16035</a>] Allow non-finalizable objects such as <code>Integer</code>, static <code>Symbol</code> etc in <code>ObjectSpace::WeakMap</code>
</li>
<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://bugs.ruby-lang.org/issues/16038">#16038</a>] Provide a public <code>WeakMap</code> which compare by equality rather than identity</li>
</ul> Ruby master - Misc #15996: DevelopersMeeting20190829Japanhttps://bugs.ruby-lang.org/issues/15996?journal_id=804252019-08-07T03:04:57Zko1 (Koichi Sasada)
<ul><li><strong>Description</strong> updated (<a title="View differences" href="/journals/80425/diff?detail_id=54090">diff</a>)</li></ul><p>Schedule was changed!!</p>
<p>Before: 2019/08/20 (Thu) 13:00-17:00 (JST)<br>
After: 2019/08/29 (Thu) 13:00-17:00 (JST)</p>
<p>Thanks,<br>
Koichi</p> Ruby master - Misc #15996: DevelopersMeeting20190829Japanhttps://bugs.ruby-lang.org/issues/15996?journal_id=804262019-08-07T03:06:23Zko1 (Koichi Sasada)
<ul><li><strong>Subject</strong> changed from <i>DevelopersMeeting20190820Japan</i> to <i>DevelopersMeeting20190829Japan</i></li></ul> Ruby master - Misc #15996: DevelopersMeeting20190829Japanhttps://bugs.ruby-lang.org/issues/15996?journal_id=804382019-08-07T13:10:34Znobu (Nobuyoshi Nakada)nobu@ruby-lang.org
<ul></ul><p>This was a missed carry-over on the last month.</p>
<ul>
<li>[Bug <a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Bug: Detecting BOM with non-UTF encoding (Closed)" href="https://bugs.ruby-lang.org/issues/15908">#15908</a>] Detecting BOM with non-UTF encoding</li>
</ul> Ruby master - Misc #15996: DevelopersMeeting20190829Japanhttps://bugs.ruby-lang.org/issues/15996?journal_id=805972019-08-11T10:35:35Zzverok (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.generate (Closed)" href="https://bugs.ruby-lang.org/issues/14781">#14781</a>] <code>Enumerator.generate</code>. Patch provided; Matz seem to have liked the idea and name proposed, can we have it in 2.7?</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://bugs.ruby-lang.org/issues/14784">#14784</a>] <code>Comparable#clamp</code> with a range. Implementation details are discussed, but generally proposal seem to be acceptable? Can we have it in 2.7, should I provide a patch?</li>
</ul> Ruby master - Misc #15996: DevelopersMeeting20190829Japanhttps://bugs.ruby-lang.org/issues/15996?journal_id=807062019-08-13T09:29:26Zmtsmfm (Fumiaki Matsushima)mtsmfm@gmail.com
<ul></ul><ul>
<li>[Feature <a class="issue tracker-2 status-1 priority-4 priority-default" title="Feature: Add option to raise NoMethodError for OpenStruct (Open)" href="https://bugs.ruby-lang.org/issues/15815">#15815</a>] Add option to raise NoMethodError for OpenStruct (mtsmfm)
<ul>
<li>We can use <code>Symbol#to_proc</code> with enumerable stuff when we use OpenStruct instead of Hash. For example: <code>OpenStruct.new(JSON.parse(users)).map(&:id)</code>
</li>
<li>But it can't prevent typo. For <code>Hash</code>, it has <code>Hash#fetch</code> to raise KeyError.</li>
</ul>
</li>
</ul> Ruby master - Misc #15996: DevelopersMeeting20190829Japanhttps://bugs.ruby-lang.org/issues/15996?journal_id=807522019-08-14T12:40:32Znobu (Nobuyoshi Nakada)nobu@ruby-lang.org
<ul></ul><ul>
<li>[Feature <a class="issue tracker-2 status-5 priority-4 priority-default closed" title="Feature: Make the dot-colon method reference frozen (Closed)" href="https://bugs.ruby-lang.org/issues/16103">#16103</a>] Make the dot-colon method reference frozen</li>
</ul> Ruby master - Misc #15996: DevelopersMeeting20190829Japanhttps://bugs.ruby-lang.org/issues/15996?journal_id=808922019-08-21T14:06:08Zk0kubun (Takashi Kokubun)takashikkbn@gmail.com
<ul></ul><ul>
<li>
<del>[Misc <a class="issue tracker-5 status-5 priority-4 priority-default closed" title="Misc: Reduce the possibility of "expand tabs" commit occurrences (Closed)" href="https://bugs.ruby-lang.org/issues/16112">#16112</a>] Reduce the possibility of "expand tabs" commit occurrences</del>
<ul>
<li>Never mind. Resolved before the MTG thanks to @jeremyevans's comment.</li>
</ul>
</li>
</ul> Ruby master - Misc #15996: DevelopersMeeting20190829Japanhttps://bugs.ruby-lang.org/issues/15996?journal_id=809042019-08-22T00:09:24Zmrkn (Kenta Murata)muraken@gmail.com
<ul></ul><ul>
<li>[Feature <a class="issue tracker-2 status-1 priority-4 priority-default" title="Feature: Proposal: Add methods to determine if it is an infinite range (Open)" href="https://bugs.ruby-lang.org/issues/15864">#15864</a>] Proposal: Add methods to determine if it is an infinite range
<ul>
<li>I proposed some candidates from mathematical terms</li>
</ul>
</li>
</ul> Ruby master - Misc #15996: DevelopersMeeting20190829Japanhttps://bugs.ruby-lang.org/issues/15996?journal_id=809052019-08-22T00:47:43Zmame (Yusuke Endoh)mame@ruby-lang.org
<ul></ul><ul>
<li>[Feature#14183] "Real" keyword argument
<ul>
<li>Jeremy and I agreed with Jeremy's proposal. I'd like to ask for matz's final confirmation.</li>
</ul>
</li>
</ul> Ruby master - Misc #15996: DevelopersMeeting20190829Japanhttps://bugs.ruby-lang.org/issues/15996?journal_id=809252019-08-23T00:56:20Zmame (Yusuke Endoh)mame@ruby-lang.org
<ul></ul><ul>
<li>[Feature <a class="issue tracker-2 status-1 priority-4 priority-default" title="Feature: Keyword arguments from method calls or ignore extra hash keys in splat (Open)" href="https://bugs.ruby-lang.org/issues/16115">#16115</a>] Keyword arguments from method calls or ignore extra hash keys in splat
<ul>
<li>It proposes a triple splat (<code>foo(***opt)</code>) to pass a keyword hash with filtering out unknown keywords. What do you think?</li>
</ul>
</li>
</ul> Ruby master - Misc #15996: DevelopersMeeting20190829Japanhttps://bugs.ruby-lang.org/issues/15996?journal_id=809292019-08-23T02:44:24Zmame (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: UnboundMethod#apply (Closed)" href="https://bugs.ruby-lang.org/issues/15955">#15955</a>] UnboundMethod#apply
<ul>
<li>The ticket proposes a shortcut to <code>unbound_method.bind(obj).call(args...)</code> without allocation of a Method object. There are some use cases, and looks reasonable to me. What do you think?</li>
</ul>
</li>
</ul> Ruby master - Misc #15996: DevelopersMeeting20190829Japanhttps://bugs.ruby-lang.org/issues/15996?journal_id=809362019-08-23T09:13:27Zosyo (manga osyo)
<ul></ul><ul>
<li>[Feature <a class="issue tracker-2 status-1 priority-4 priority-default" title="Feature: Allow questionmarks in variable names (Open)" href="https://bugs.ruby-lang.org/issues/15991">#15991</a>] Allow questionmarks in variable names
<ul>
<li>Proposal: Allow <code>?</code> in variable names</li>
<li>In <a class="issue tracker-2 status-2 priority-4 priority-default" title="Feature: Query attributes (attribute methods ending in `?` mark) (Assigned)" href="https://bugs.ruby-lang.org/issues/5781">#5781</a>, matz is explicitly against an instance variable that ends with <code>?</code>
</li>
<li>How about allowing only local variables ?</li>
</ul>
</li>
</ul> Ruby master - Misc #15996: DevelopersMeeting20190829Japanhttps://bugs.ruby-lang.org/issues/15996?journal_id=809412019-08-23T17:43:32Zzverok (Victor Shepelev)zverok.offline@gmail.com
<ul></ul><ul>
<li>[Feature <a class="issue tracker-2 status-1 priority-4 priority-default" title="Feature: Partial application (Open)" href="https://bugs.ruby-lang.org/issues/16113">#16113</a>] Partial application: <code>fetch(urls).map(&JSON.:parse.w(symbolize_names: true))</code>
</li>
<li>[Feature <a class="issue tracker-2 status-5 priority-4 priority-default closed" title="Feature: Data: simple immutable value object (Closed)" href="https://bugs.ruby-lang.org/issues/16122">#16122</a>] <code>Struct::Value</code>: simple immutable value object</li>
</ul> Ruby master - Misc #15996: DevelopersMeeting20190829Japanhttps://bugs.ruby-lang.org/issues/15996?journal_id=810622019-08-26T22:11:44ZDan0042 (Daniel DeLorme)
<ul></ul><ul>
<li>[Feature <a class="issue tracker-2 status-1 priority-4 priority-default" title="Feature: Add to_proc method to the Array class (Open)" href="https://bugs.ruby-lang.org/issues/10829">#10829</a>] Add to_proc method to the Array class</li>
<li>[Feature <a class="issue tracker-2 status-1 priority-4 priority-default" title="Feature: Add Symbol#call to allow to_proc shorthand with arguments (Open)" href="https://bugs.ruby-lang.org/issues/12115">#12115</a>] Add Symbol#call to allow to_proc shorthand with arguments</li>
<li>[Feature <a class="issue tracker-2 status-1 priority-4 priority-default" title="Feature: Proc#with and Proc#by, for partial function application and currying (Open)" href="https://bugs.ruby-lang.org/issues/15302">#15302</a>] Proc#with and Proc#by, for partial function application and currying</li>
<li>[Misc <a class="issue tracker-5 status-7 priority-4 priority-default closed" title="Misc: Reconsider numbered parameters (Feedback)" href="https://bugs.ruby-lang.org/issues/15723">#15723</a>] Reconsider numbered parameters</li>
<li>[Feature <a class="issue tracker-2 status-5 priority-4 priority-default closed" title="Feature: `it` as a default block parameter (Closed)" href="https://bugs.ruby-lang.org/issues/15897">#15897</a>] <code>it</code> as a default block parameter</li>
<li>[Feature <a class="issue tracker-2 status-1 priority-4 priority-default" title="Feature: Partial application (Open)" href="https://bugs.ruby-lang.org/issues/16113">#16113</a>] Partial application</li>
<li>[Feature <a class="issue tracker-2 status-6 priority-4 priority-default closed" title="Feature: Omitted block argument if block starts with dot-method call (Rejected)" href="https://bugs.ruby-lang.org/issues/16120">#16120</a>] Implicit block argument if block starts with dot-method call
<ul>
<li>All proposals above are different ideas for a block shorthand more versatile than <code>(&:to_s)</code>
</li>
<li>Insatisfaction with numbered parameters solution</li>
<li>In <a class="issue tracker-2 status-6 priority-4 priority-default closed" title="Feature: Omitted block argument if block starts with dot-method call (Rejected)" href="https://bugs.ruby-lang.org/issues/16120">#16120</a> I try to analyze the root issue common to all the above</li>
</ul>
</li>
</ul> Ruby master - Misc #15996: DevelopersMeeting20190829Japanhttps://bugs.ruby-lang.org/issues/15996?journal_id=810812019-08-27T10:23:23Zduerst (Martin Dürst)duerst@it.aoyama.ac.jp
<ul></ul><p>Dan0042 (Daniel DeLorme) wrote:</p>
<blockquote>
<ul>
<li>[Feature <a class="issue tracker-2 status-1 priority-4 priority-default" title="Feature: Add to_proc method to the Array class (Open)" href="https://bugs.ruby-lang.org/issues/10829">#10829</a>] Add to_proc method to the Array class</li>
<li>[Feature <a class="issue tracker-2 status-1 priority-4 priority-default" title="Feature: Add Symbol#call to allow to_proc shorthand with arguments (Open)" href="https://bugs.ruby-lang.org/issues/12115">#12115</a>] Add Symbol#call to allow to_proc shorthand with arguments</li>
<li>[Feature <a class="issue tracker-2 status-1 priority-4 priority-default" title="Feature: Proc#with and Proc#by, for partial function application and currying (Open)" href="https://bugs.ruby-lang.org/issues/15302">#15302</a>] Proc#with and Proc#by, for partial function application and currying</li>
<li>[Misc <a class="issue tracker-5 status-7 priority-4 priority-default closed" title="Misc: Reconsider numbered parameters (Feedback)" href="https://bugs.ruby-lang.org/issues/15723">#15723</a>] Reconsider numbered parameters</li>
<li>[Feature <a class="issue tracker-2 status-5 priority-4 priority-default closed" title="Feature: `it` as a default block parameter (Closed)" href="https://bugs.ruby-lang.org/issues/15897">#15897</a>] <code>it</code> as a default block parameter</li>
<li>[Feature <a class="issue tracker-2 status-1 priority-4 priority-default" title="Feature: Partial application (Open)" href="https://bugs.ruby-lang.org/issues/16113">#16113</a>] Partial application</li>
<li>[Feature <a class="issue tracker-2 status-6 priority-4 priority-default closed" title="Feature: Omitted block argument if block starts with dot-method call (Rejected)" href="https://bugs.ruby-lang.org/issues/16120">#16120</a>] Implicit block argument if block starts with dot-method call
<ul>
<li>All proposals above are different ideas for a block shorthand more versatile than <code>(&:to_s)</code>
</li>
<li>Insatisfaction with numbered parameters solution</li>
<li>In <a class="issue tracker-2 status-6 priority-4 priority-default closed" title="Feature: Omitted block argument if block starts with dot-method call (Rejected)" href="https://bugs.ruby-lang.org/issues/16120">#16120</a> I try to analyze the root issue common to all the above</li>
</ul>
</li>
</ul>
</blockquote>
<p>I know I shouldn't comment on individual issues here, but I haven't found a better way of commenting on this group of issues (maybe we should create a superissue): I think we should stop dealing with individual ideas of how to improve functional programming in Ruby and work out an overview of what's missing and how to address it, understanding that Ruby is first and foremost an OO language and we'll never get to the same point as Haskell or something similar.</p> Ruby master - Misc #15996: DevelopersMeeting20190829Japanhttps://bugs.ruby-lang.org/issues/15996?journal_id=810822019-08-27T11:04:22Zshevegen (Robert A. Heiler)shevegen@gmail.com
<ul></ul><blockquote>
<p>I know I shouldn't comment on individual issues here</p>
</blockquote>
<p>While I agree, one problem is that e. g. Dan0042 did not read the prior comments here - in<br>
particular he linked in "[Misc <a class="issue tracker-5 status-7 priority-4 priority-default closed" title="Misc: Reconsider numbered parameters (Feedback)" href="https://bugs.ruby-lang.org/issues/15723">#15723</a>] Reconsider numbered parameters", which already was<br>
linked in by sikachu. IMO, these issues become quite a lot of discussion work in general<br>
and I am not sure matz has enough time to comment on every single one when people just<br>
copy/paste new issues without looking whether others already linked these in. :\</p>
<p>Otherwise I agree with Martin's statement of "work out an overview of what's missing and<br>
how to address it", in regards to the functional approach. I myself use ruby almost<br>
exclusively from an OOP view (mostly); other ruby users seem to like a more functional<br>
approach, such as zverok. Sometimes these styles seem to clash, in my opinion.</p>
<p>The dev-meeting discussions are great for others in the ruby community who are not e. g.<br>
in japan, but this here is probably the longest individual issue tracker for any dev<br>
meeting as of yet; I am not sure it is possible to discuss all of this in e. g. 4 hours.<br>
But I digress too, apologies for that.</p> Ruby master - Misc #15996: DevelopersMeeting20190829Japanhttps://bugs.ruby-lang.org/issues/15996?journal_id=810872019-08-27T14:56:19ZDan0042 (Daniel DeLorme)
<ul></ul><p>My apologies if I did something inappropriate. I <em>did</em> realize there was some duplication, I just thought these issues should be considered part of a single "package". 100% agree with <a class="user active user-mention" href="https://bugs.ruby-lang.org/users/50">@duerst (Martin Dürst)</a>, what he describes is what I was trying to do.</p> Ruby master - Misc #15996: DevelopersMeeting20190829Japanhttps://bugs.ruby-lang.org/issues/15996?journal_id=812222019-08-28T03:07:03Zmame (Yusuke Endoh)mame@ruby-lang.org
<ul></ul><p>Looks like we have too many topics at the next meeting. Please do not expect all tickets to be discussed. Thank you for your understanding.</p> Ruby master - Misc #15996: DevelopersMeeting20190829Japanhttps://bugs.ruby-lang.org/issues/15996?journal_id=812262019-08-28T08:17:36Zmame (Yusuke Endoh)mame@ruby-lang.org
<ul></ul><p>zverok (Victor Shepelev) wrote:</p>
<blockquote>
<ul>
<li>[Feature <a class="issue tracker-2 status-5 priority-4 priority-default closed" title="Feature: Enumerator.generate (Closed)" href="https://bugs.ruby-lang.org/issues/14781">#14781</a>] <code>Enumerator.generate</code>. Patch provided; Matz seem to have liked the idea and name proposed, can we have it in 2.7?</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://bugs.ruby-lang.org/issues/14784">#14784</a>] <code>Comparable#clamp</code> with a range. Implementation details are discussed, but generally proposal seem to be acceptable? Can we have it in 2.7, should I provide a patch?</li>
</ul>
</blockquote>
<p>The two tickets were discussed at the past meetings. Next time, could you give us more informative short summary instead of "can we have it in 2.7?" We need to spend time to read the ticket to grab the progress from the previous discussion.<br>
For example, the first issue is mainly a naming issue, so it would be helpful to list the proposed names. In the second one, akr pointed out the spec issue. (Do not call it "implementation details.") "Raising an exception is proposed for clamp(1...2)" would be even helpful.</p>
<p><a class="user active user-mention" href="https://bugs.ruby-lang.org/users/710">@zverok (Victor Shepelev)</a> Sorry for picking only your agenda, but for all people, please consider saving our time (especially matz's).</p> Ruby master - Misc #15996: DevelopersMeeting20190829Japanhttps://bugs.ruby-lang.org/issues/15996?journal_id=812282019-08-28T11:44:48Zzverok (Victor Shepelev)zverok.offline@gmail.com
<ul></ul><p><a class="user active user-mention" href="https://bugs.ruby-lang.org/users/18">@mame (Yusuke Endoh)</a> OK, sorry. I was not sure how the process looks internally (e.g. should I save the space and attention of the reader in agenda by just listing things shortly, or provide the full context in-place). Here are updated descriptions, just in case:</p>
<ul>
<li>[Feature <a class="issue tracker-2 status-5 priority-4 priority-default closed" title="Feature: Enumerator.generate (Closed)" href="https://bugs.ruby-lang.org/issues/14781">#14781</a>] <code>Enumerator.generate</code>: Matz seems to have liked the idea and name proposed; implementation patch provided; the name should be decided upon: either <code>generate</code>, or, maybe, <code>produce</code> (looking like more-or-less oppose to <code>reduce</code>)</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://bugs.ruby-lang.org/issues/14784">#14784</a>] <code>Comparable#clamp</code> with a range. The issue generally agreed on, except for behavior with upper bound with excluding-end range. <code>ArgumentError</code> is proposed for this case.</li>
</ul> Ruby master - Misc #15996: DevelopersMeeting20190829Japanhttps://bugs.ruby-lang.org/issues/15996?journal_id=812292019-08-28T13:27:48Zmame (Yusuke Endoh)mame@ruby-lang.org
<ul></ul><p><a class="user active user-mention" href="https://bugs.ruby-lang.org/users/710">@zverok (Victor Shepelev)</a> Thank you!</p> Ruby master - Misc #15996: DevelopersMeeting20190829Japanhttps://bugs.ruby-lang.org/issues/15996?journal_id=814642019-09-08T12:41:51Zmame (Yusuke Endoh)mame@ruby-lang.org
<ul><li><strong>Status</strong> changed from <i>Open</i> to <i>Closed</i></li></ul>