[#78633] ruby/spec needs help from CRuby committers — Benoit Daloze <eregontp@...>
Currently, ruby/spec is maintained mostly by individuals and enjoys the
13 messages
2016/12/13
[#78963] Re: ruby/spec needs help from CRuby committers
— Urabe Shyouhei <shyouhei@...>
2017/01/04
I did ask attendees of last developer meeting to join this
[#78642] Re: ruby/spec needs help from CRuby committers
— Eric Wong <normalperson@...>
2016/12/14
Benoit Daloze <eregontp@gmail.com> wrote:
[ruby-core:78515] [Ruby trunk Feature#12813] Calling chunk_while, slice_after, slice_before, slice_when with no block
From:
matz@...
Date:
2016-12-06 12:58:49 UTC
List:
ruby-core #78515
Issue #12813 has been updated by Yukihiro Matsumoto. After consideration, I accept this proposal. Matz. ---------------------------------------- Feature #12813: Calling chunk_while, slice_after, slice_before, slice_when with no block https://bugs.ruby-lang.org/issues/12813#change-61895 * Author: Marc-Andre Lafortune * Status: Assigned * Priority: Normal * Assignee: Yukihiro Matsumoto ---------------------------------------- Currently, `chunk_while`, `slice_after`, `slice_before`, `slice_when` all require a block. If one needs the index within the block, there is no good way to do this; `enum.each_with_index.chunk_while` would have indices in the results, so `enum.enum_for(:chunk_while).with_index` is the best solution. I feel that we should return `enum_for(:chunk_while)`. This is strictly more useful than raising as we currently do. -- https://bugs.ruby-lang.org/ Unsubscribe: <mailto:ruby-core-request@ruby-lang.org?subject=unsubscribe> <http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>