I would prefer to change them all: mapped, filtered, flatMapped, reduced, and flattened. <span></span><br><br>On Friday, 8 April 2016, David Waite via swift-evolution <<a href="mailto:swift-evolution@swift.org">swift-evolution@swift.org</a>> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">In the sense that these are existing terms of art from functional programming, they inherit the meaning of being non-mutating.<br>
<br>
If we did consider changing the name of one, I’d prefer if we considered all of them at once (so the various bike sheds would be painted in complementary colors)<br>
<br>
-DW<br>
<br>
> On Apr 7, 2016, at 12:12 PM, Dave Abrahams via swift-evolution <<a href="javascript:;" onclick="_e(event, 'cvml', 'swift-evolution@swift.org')">swift-evolution@swift.org</a>> wrote:<br>
><br>
><br>
> on Thu Apr 07 2016, Arsen Gasparyan <<a href="javascript:;" onclick="_e(event, 'cvml', 'swift-evolution@swift.org')">swift-evolution@swift.org</a>> wrote:<br>
><br>
>> Hey guys,<br>
>><br>
>> The 'flatten()' method didn't get the Swift 3 API renaming treatment it should<br>
>> have, to go along with reversed, sorted, joined, etc.<br>
>> As I see Dmitri Gribenko already agree with it but we still have to discuss it<br>
>> here. So what do you think?<br>
>><br>
>> Implementation: <a href="https://github.com/apple/swift/pull/2038" target="_blank">https://github.com/apple/swift/pull/2038</a><br>
><br>
> I am agnostic on this, but should explain the rationale for the current<br>
> name. It wasn't overlooked. We kept flatten as is because it is part of<br>
> a suite of methods that are terms of art from functional programming<br>
> (map, filter, flatMap, reduce) that don't follow the naming guidelines<br>
> but we are nonetheless leaving alone. The fact that the semantics of<br>
> flatMap can only be sensibly described in terms of map and flatten<br>
> reinforces this rationale.<br>
><br>
> If we want to change flatten, we should decide whether this is a<br>
> principled change, and if so, what the principle is. If it's a change<br>
> simply because “flatten() feels weird,” that's OK too, but we should<br>
> understand what we're doing and why.<br>
><br>
> --<br>
> Dave<br>
><br>
> _______________________________________________<br>
> swift-evolution mailing list<br>
> <a href="javascript:;" onclick="_e(event, 'cvml', 'swift-evolution@swift.org')">swift-evolution@swift.org</a><br>
> <a href="https://lists.swift.org/mailman/listinfo/swift-evolution" target="_blank">https://lists.swift.org/mailman/listinfo/swift-evolution</a><br>
<br>
_______________________________________________<br>
swift-evolution mailing list<br>
<a href="javascript:;" onclick="_e(event, 'cvml', 'swift-evolution@swift.org')">swift-evolution@swift.org</a><br>
<a href="https://lists.swift.org/mailman/listinfo/swift-evolution" target="_blank">https://lists.swift.org/mailman/listinfo/swift-evolution</a><br>
</blockquote><br><br>-- <br>-- Howard.<br>