[swift-evolution] [Accepted with Revision] SE-0094: Add sequence(initial:next:) and sequence(state:next:) to the stdlib

Jacob Bandes-Storch jtbandes at gmail.com
Wed May 25 21:54:02 CDT 2016

Great news!

I've filed a bug for this in JIRA: https://bugs.swift.org/browse/SR-1622

On Wed, May 25, 2016 at 7:44 PM, Chris Lattner via swift-evolution <
swift-evolution at swift.org> wrote:

> Proposal Link:
> https://github.com/apple/swift-evolution/blob/master/proposals/0094-sequence-function.md
> 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 as-is.
> 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
> https://lists.swift.org/mailman/listinfo/swift-evolution
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.swift.org/pipermail/swift-evolution/attachments/20160525/34c0e34e/attachment.html>

More information about the swift-evolution mailing list