[swift-evolution] Fw: Re: [Proposal Draft] Literal Syntax Protocols

Matthew Johnson matthew at anandabits.com
Fri Jun 24 10:25:41 CDT 2016

The design in this proposal comes from the standard library team.  The intent is for the use of underscore here to be consistent with other uses of underscore prefix in the standard library.  I’m not sure why you think this is different than the rest...

> On Jun 24, 2016, at 10:22 AM, Adrian Zubarev via swift-evolution <swift-evolution at swift.org> wrote:
> I’m aware of that fact, but all types with underscore even in the stdlib telling me to keep my hands of them, because something might happen to them.
> As an example we have _Strideable protocol which is visible by its name, but its declaration isn’t visible at all:
> // FIXME(ABI)(compiler limitation): Remove `_Strideable`.
> // WORKAROUND rdar://25214598 <rdar://25214598> - should be:
> // protocol Strideable : Comparable {...}
> % for Self in ['_Strideable', 'Strideable']:
> From Stride.swift.gyb <https://github.com/apple/swift/blob/63c36dff0a327874a5041d46335bde314bc108d8/stdlib/public/core/Stride.swift.gyb>
> -- 
> Adrian Zubarev
> Sent with Airmail
> Am 24. Juni 2016 um 17:09:53, Matthew Johnson (matthew at anandabits.com <mailto:matthew at anandabits.com>) schrieb:
>> The underscore is used in the same way it is used elsewhere in the standard library.  The protocols must be public because they need to be visible to user code in order for the design to work correctly.  However, they are considered implementation details that users really shouldn’t know about.  This pattern is well established in the standard library.
> _______________________________________________
> swift-evolution mailing list
> swift-evolution at swift.org <mailto:swift-evolution at swift.org>
> https://lists.swift.org/mailman/listinfo/swift-evolution <https://lists.swift.org/mailman/listinfo/swift-evolution>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.swift.org/pipermail/swift-evolution/attachments/20160624/1da02435/attachment.html>

More information about the swift-evolution mailing list