[swift-evolution] [swift-evolution-announce] [Review] SE-0041: Updating Protocol Naming Conventions for Conversions
Patrick Smith
pgwsmith at gmail.com
Tue May 10 22:14:58 CDT 2016
How about:
Consuming (from)
Producing (to)
IntegerLiteralConsuming
StringLiteralConsuming
CustomStringProducing
CustomDebugStringProducing
As for something that does both, all I could find was ‘bidirectional’, ‘two-way’, ‘mutual’, ‘duplex’. I tried searching in biology (https://en.wikipedia.org/wiki/Organic_reaction), but couldn’t find anything. I like the idea of just conforming to both protocols, and some sort of protocol typealias. Or staying with Representable.
> On 11 May 2016, at 12:33 PM, Erica Sadun via swift-evolution <swift-evolution at swift.org> wrote:
>
>>
>> On May 10, 2016, at 6:51 PM, Chris Lattner via swift-evolution <swift-evolution at swift.org> wrote:
>>
>>
>>> On May 10, 2016, at 11:48 AM, Chris Lattner <clattner at apple.com> wrote:
>>>
>>> Hello Swift community,
>>>
>>> The review of "SE-0041: Updating Protocol Naming Conventions for Conversions" begins now and runs through May 16. The proposal is available here:
>>>
>>> https://github.com/apple/swift-evolution/blob/master/proposals/0041-conversion-protocol-conventions.md
>>
>> Here are comments from someone who preferred to stay anonymous. These are not my own:
>>
>>
>>
>>
>> * What is your evaluation of the proposal?
>>
>> I rather agree with the comments mentioned in the proposal from the Standard Library design team, in that I agree with the basic intention of the proposal, but I’m not convinced about the proposed answer. Specifically:
>
>
> We'd be happy to bikeshed again.
>
> I think fundamentally our take on this is:
>
> * We want there to be a standard that expresses the three conversion/initialization styles.
> * We feel the system is currently broken. And we want to have a coherent and settled vision in place for 3, even imperfect.
> * We're flexible about the naming but it should be (1) Swifty and (2) well grounded in meaning.
>
> Let me turn the floor over to Matthew here.
>
> -- E
>
> _______________________________________________
> 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