+1
> On Nov 7, 2017, at 6:23 PM, John McCall <rjmcc...@apple.com> wrote:
>
> • What is your evaluation of the proposal?
BJ summarized my thoughts nicely. I think “flatMap” in its current form is
confusing to both newcomers and functional programmers familiar with the
nomenclature. I’ve been aware of this disparity and thought about it for
awhile. I typically redefine “flatMap” as “mapOptional” in my projects for
clarity.
> • Is the problem being addressed significant enough to warrant a change
> to Swift?
I think so! It improves the user experience in a significant way to those that
encounter the function in the wild.
> • Does this proposal fit well with the feel and direction of Swift?
Yes.
> • If you have used other languages or libraries with a similar feature,
> how do you feel that this proposal compares to those?
It fits in well. Swift’s current extra implementation of “flatMap” is the
anomaly.
> • How much effort did you put into your review? A glance, a quick
> reading, or an in-depth study?
Gave a quick reading to the proposal.
_______________________________________________
swift-evolution mailing list
swift-evolution@swift.org
https://lists.swift.org/mailman/listinfo/swift-evolution
