<div dir="ltr">At this stage, it's rather confuse to me, if return boolean, probably sizeOf and boolOf is easier for me.<div><br></div><div>boolOf(equalTo:)<br></div><div>boolOf(matching:)<br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Sat, Apr 1, 2017 at 10:54 PM, Rien via swift-evolution <span dir="ltr"><<a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class=""><br>
> On 01 Apr 2017, at 16:10, David Hart <<a href="mailto:david@hartbit.com">david@hartbit.com</a>> wrote:<br>
><br>
>><br>
>> On 1 Apr 2017, at 11:32, Rien <Rien@Balancingrock.nl> wrote:<br>
>><br>
>><br>
>>> On 01 Apr 2017, at 10:47, Xiaodi Wu via swift-evolution <<a href="mailto:swift-evolution@swift.org">swift-evolution@swift.org</a>> wrote:<br>
>>><br>
>>> On Sat, Apr 1, 2017 at 3:40 AM, David Hart via swift-evolution <<a href="mailto:swift-evolution@swift.org">swift-evolution@swift.org</a>> wrote:<br>
>>><br>
>>>> On 1 Apr 2017, at 09:50, Brandon Trussell <<a href="mailto:brandon2k3@gmail.com">brandon2k3@gmail.com</a>> wrote:<br>
>>>><br>
>>>> I agree that based on the method name, I thought a collection would be returned.<br>
>>><br>
>>> Now that I think more about it, I think you're right. It is confusing. Perhaps:<br>
>>><br>
>>> allAre(equalTo: )<br>
>>> allAre(matching: )<br>
>>><br>
>>> Well, if we're going to go full stdlib naming guidelines, shouldn't they be--<br>
>>><br>
>>> ```<br>
>>> areAll(equalTo:)<br>
>>> areAll(matching:)<br>
>>> ```<br>
>><br>
>><br>
>> thatAre(equalTo: )<br>
>> thatAre(matching: )<br>
><br>
> That would be confusing again. You'd get the impression that the functions are returning elements of the Sequence, not a Bool.<br>
<br>
</span>Yup. my bad.<br>
<br>
Rien.<br>
<div class="HOEnZb"><div class="h5"><br>
<br>
><br>
>> Regards,<br>
>> Rien<br>
>><br>
>> Site: <a href="http://balancingrock.nl" rel="noreferrer" target="_blank">http://balancingrock.nl</a><br>
>> Blog: <a href="http://swiftrien.blogspot.com" rel="noreferrer" target="_blank">http://swiftrien.blogspot.com</a><br>
>> Github: <a href="http://github.com/Balancingrock" rel="noreferrer" target="_blank">http://github.com/<wbr>Balancingrock</a><br>
>> Project: <a href="http://swiftfire.nl" rel="noreferrer" target="_blank">http://swiftfire.nl</a><br>
>><br>
>><br>
>>><br>
>>>> On Sat, Apr 1, 2017 at 12:36 AM, David Hart via swift-evolution <<a href="mailto:swift-evolution@swift.org">swift-evolution@swift.org</a>> wrote:<br>
>>>><br>
>>>><br>
>>>>> On 1 Apr 2017, at 06:02, Will Stanton via swift-evolution <<a href="mailto:swift-evolution@swift.org">swift-evolution@swift.org</a>> wrote:<br>
>>>>><br>
>>>>> +1 to adding, but the name `all` suggests (to me) the return of another sequence, not a Bool.<br>
>>>><br>
>>>> I'm not too concerned because the mandatory labels makes it clear.<br>
>>>><br>
>>>>> Perhaps the function name should be question-like?<br>
>>>>><br>
>>>>> Suggesting: `membersSatisfy(condition:)` or `allSatisfy(condition:)` or maybe even just `satisfies(condition:)`<br>
>>>>> The question-like modifier/verb is necessary to suggest a Bool and IMO not a needless word.<br>
>>>>><br>
>>>>> Regards,<br>
>>>>> Will Stanton<br>
>>>>><br>
>>>>>> On Mar 31, 2017, at 11:28, Ben Cohen via swift-evolution <<a href="mailto:swift-evolution@swift.org">swift-evolution@swift.org</a>> wrote:<br>
>>>>>><br>
>>>>>> Hopefully non-controversial, aside from the naming of the method and arguments, about which controversy abounds<br>
>>>>><br>
>>>>> ______________________________<wbr>_________________<br>
>>>>> swift-evolution mailing list<br>
>>>>> <a href="mailto:swift-evolution@swift.org">swift-evolution@swift.org</a><br>
>>>>> <a href="https://lists.swift.org/mailman/listinfo/swift-evolution" rel="noreferrer" target="_blank">https://lists.swift.org/<wbr>mailman/listinfo/swift-<wbr>evolution</a><br>
>>>><br>
>>>> ______________________________<wbr>_________________<br>
>>>> swift-evolution mailing list<br>
>>>> <a href="mailto:swift-evolution@swift.org">swift-evolution@swift.org</a><br>
>>>> <a href="https://lists.swift.org/mailman/listinfo/swift-evolution" rel="noreferrer" target="_blank">https://lists.swift.org/<wbr>mailman/listinfo/swift-<wbr>evolution</a><br>
>>>><br>
>>>><br>
>>>><br>
>>>> --<br>
>>>> Brandon<br>
>>><br>
>>> ______________________________<wbr>_________________<br>
>>> swift-evolution mailing list<br>
>>> <a href="mailto:swift-evolution@swift.org">swift-evolution@swift.org</a><br>
>>> <a href="https://lists.swift.org/mailman/listinfo/swift-evolution" rel="noreferrer" target="_blank">https://lists.swift.org/<wbr>mailman/listinfo/swift-<wbr>evolution</a><br>
>>><br>
>>><br>
>>> ______________________________<wbr>_________________<br>
>>> swift-evolution mailing list<br>
>>> <a href="mailto:swift-evolution@swift.org">swift-evolution@swift.org</a><br>
>>> <a href="https://lists.swift.org/mailman/listinfo/swift-evolution" rel="noreferrer" target="_blank">https://lists.swift.org/<wbr>mailman/listinfo/swift-<wbr>evolution</a><br>
<br>
______________________________<wbr>_________________<br>
swift-evolution mailing list<br>
<a href="mailto:swift-evolution@swift.org">swift-evolution@swift.org</a><br>
<a href="https://lists.swift.org/mailman/listinfo/swift-evolution" rel="noreferrer" target="_blank">https://lists.swift.org/<wbr>mailman/listinfo/swift-<wbr>evolution</a><br>
</div></div></blockquote></div><br></div>