[swift-evolution] [Review] SE-0094: Add sequence(initial:next:) and sequence(state:next:) to the stdlib
jeremy.j.pereira at googlemail.com
Mon May 23 07:44:05 CDT 2016
> On 19 May 2016, at 23:29, Chris Lattner via swift-evolution <swift-evolution at swift.org> wrote:
> * What is your evaluation of the proposal?
I think I would find myself using this in loads of places, if it was implemented.
One question: what is the downside of making these functions `rethrows` and allowing the closure to throw?
> * Is the problem being addressed significant enough to warrant a change to Swift?
Yes. I probably implement something similar to this in every project.
> * Does this proposal fit well with the feel and direction of Swift?
> * If you have used other languages or libraries with a similar feature, how do you feel that this proposal compares to those?
I’ve dabbled in Haskell but I wouldn’t claim to have used its equivalent of this feature.
> * How much effort did you put into your review? A glance, a quick reading, or an in-depth study?
I read the proposal and the previous responses.
> More information about the Swift evolution process is available at
> Thank you,
> -Chris Lattner
> Review Manager
> swift-evolution mailing list
> swift-evolution at swift.org
More information about the swift-evolution