[swift-evolution] When to use argument labels, part DEUX
Matthew Judge
matthew.judge at gmail.com
Mon Feb 8 05:47:42 CST 2016
Agree that basing the preposition location on whether there is a default value is unfortunate. The problem is "Zone" is not redundant/needless when calling it with the default value.
copyWith()
If I were asking "what zone?" Ok it's the default zone, but I'm just asking "with what?"
> On Feb 7, 2016, at 10:48, Dave Abrahams via swift-evolution <swift-evolution at swift.org> wrote:
>
>
> on Sat Feb 06 2016, Douglas Gregor <swift-evolution at swift.org> wrote:
>
>>> On Feb 6, 2016, at 10:08 PM, Dave Abrahams via swift-evolution <swift-evolution at swift.org> wrote:
>>>
>>>
>>>> on Sat Feb 06 2016, Thorsten Seitz <swift-evolution at swift.org> wrote:
>>>>
>>>> So the preposition should move into the argument label if the argument is optional?
>>>>
>>>> copy(withZone: zone = nil)
>>>
>>> That's a good idea.
>>
>> It seems unfortunate that the placement of the preposition should
>> change depending on whether there is a default argument or not,
>> especially since it is reasonable to imagine that an API evolves to
>> gain a default argument later on.
>
> You're right; it would complicate the rules significantly, too.
>
>> - Doug
>>
>>>
>>>> -Thorsten
>>>>
>>>>> Am 06.02.2016 um 14:45 schrieb Matthew Judge via swift-evolution
>>>>> <swift-evolution at swift.org>:
>>>>>
>>>>> Very first method
>>>>>
>>>>> copyWith(zone: Zone = nil)
>>>>>
>>>>> can be called as
>>>>>
>>>>> copyWith()
>>>>>
>>>>> I'm assuming this is still something we don't want right?
>>>>>
>>>>>> On Feb 6, 2016, at 02:16, Douglas Gregor via swift-evolution
>>>>>> <swift-evolution at swift.org> wrote:
>>>>>>
>>>>>>
>>>>>>> On Feb 5, 2016, at 1:32 PM, Dave Abrahams via swift-evolution
>>>>>>> <swift-evolution at swift.org> wrote:
>>>>>>>
>>>>>>>
>>>>>>> Given all the awesome feedback I've gotten on this thread, I went back
>>>>>>> to the drawing board and came up with something new; I think this one
>>>>>>> works. The previously-stated goals still apply:
>>>>>>
>>>>>>> [snip goals]
>>>>>>
>>>>>>> P.S. Doug is presently working on generating new importer results, based
>>>>>>> on these guidelines, for your perusal. They should be ready soon.
>>>>>>
>>>>>>
>>>>>> Here’s a link:
>>>>>>
>>>>>> https://github.com/apple/swift-3-api-guidelines-review/pull/10/files
>>>>>>
>>>>>> Feedback welcome!
>>>>>>
>>>>>> - Doug
>>>>>>
>>>>>> _______________________________________________
>>>>>> swift-evolution mailing list
>>>>>> swift-evolution at swift.org
>>>>>> https://lists.swift.org/mailman/listinfo/swift-evolution
>>>>> _______________________________________________
>>>>> swift-evolution mailing list
>>>>> swift-evolution at swift.org
>>>>> https://lists.swift.org/mailman/listinfo/swift-evolution
>>>> _______________________________________________
>>>> swift-evolution mailing list
>>>> swift-evolution at swift.org
>>>> https://lists.swift.org/mailman/listinfo/swift-evolution
>>>
>>> --
>>> -Dave
>>>
>>> _______________________________________________
>>> swift-evolution mailing list
>>> swift-evolution at swift.org
>>> https://lists.swift.org/mailman/listinfo/swift-evolution
>>
>> _______________________________________________
>> swift-evolution mailing list
>> swift-evolution at swift.org
>> https://lists.swift.org/mailman/listinfo/swift-evolution
>
> --
> -Dave
>
> _______________________________________________
> swift-evolution mailing list
> swift-evolution at swift.org
> https://lists.swift.org/mailman/listinfo/swift-evolution
More information about the swift-evolution
mailing list