[swift-evolution] Stdlib closure argument labels and parameter names

[Dave Abrahams]

on Mon Jun 27 2016, Erica Sadun <erica-AT-ericasadun.com> wrote:

>> On Jun 27, 2016, at 1:05 PM, Dave Abrahams <dabrahams at apple.com> wrote:
>> 
>> 
>> on Mon Jun 27 2016, Erica Sadun <erica-AT-ericasadun.com <http://erica-at-ericasadun.com/>> wrote:
>> 
>
>>>> On Jun 27, 2016, at 12:02 PM, Dave Abrahams <dabrahams at apple.com> wrote:
>>>> 
>>>> 
>>>> on Mon Jun 27 2016, Erica Sadun <erica-AT-ericasadun.com> wrote:
>>>> 
>>> 
>>>>>> On Jun 27, 2016, at 8:40 AM, Dave Abrahams via swift-evolution <swift-evolution at swift.org> wrote:
>>>>>> “each” is just what's required to make “so” read sensibly.
>>>>>> 
>>>>>>  (0..<100).filter(so: isPrime)
>>>>>> 
>>>>>> doesn't make any obvious sense.
>>>>> 
>>>>> Shouldn't there be a term of art exemption for `filter(_:)`. Otherwise why not use `select(where:)`.
>>>> 
>>>> Because `where(...)` is better.  But all such changes are out of scope
>>>> here.
>>> 
>>> Are you asking/suggesting that it be in scope somewhere else or merely removing it from the
>>> conversation as tangential?
>> 
>> Yes, as I've been saying, we should take up the basenames of functional
>> methods, considering whether the terms of art should be considered
>> sacred cows, as a separate proposal.
>> 
>> -- 
>> Dave
>
> A or B?
>
> Yes.
>
> -- E, moo
> p.s. I'll start a thread

There's already
http://news.gmane.org/find-root.php?message_id=CAKA%3djdbxiC%5fq0Fe%3dXc%3dmSWu7OtGxMgAQyb0QMA6%5fOaiiLB3foA%40mail.gmail.com

I referred to it in my introduction of this thread.

-- 
Dave