[swift-evolution] [Accepted with Revision] SE-0094: Add sequence(initial:next:) and sequence(state:next:) to the stdlib
kevin at sb.org
Wed May 25 21:55:45 CDT 2016
And I've just grabbed that bug, and will whip up an initial
implementation shortly :D
I'm also going to update the proposal with the name change in a minute.
On Wed, May 25, 2016, at 07:54 PM, Jacob Bandes-Storch via swift-evolution wrote:
> Great news!
> I've filed a bug for this in JIRA:
> On Wed, May 25, 2016 at 7:44 PM, Chris Lattner via swift-evolution <swift-
> evolution at swift.org> wrote:
>> Proposal Link:
>> The review of "SE-0094: Add sequence(initial:next:) and
>> sequence(state:next:) to the stdlib" ran from May 19…23, 2016. The
>> proposal has been *accepted* with one minor naming-related change:
>> - Feedback from the community & core team is positive.
>> - Core team discussed whether it made sense to add just the first
>> form, or whether it made sense to add both. They agree that
>> although the form using an explicit state is much more
>> infrequently used, when it is necessary, it is extremely helpful
>> to have. It is also useful to consider both as a pair.
>> - On naming, the core team agrees with the community that
>> “sequence(first:next:)” is a better name than
>> "sequence(initial:next:)”. "sequence(state:next:)” is approved
>> Thank you to Kevin Ballard and Erica Sadun for proposing this both
>> in SE-0045 and in SE-0094, an implementation of these functions
>> would be welcome!
>> -Chris Lattner
>> Review Manager
>> swift-evolution mailing list
>> swift-evolution at swift.org
> swift-evolution mailing list
> swift-evolution at swift.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the swift-evolution