[swift-evolution] [Pitch] Rename protocol<> to Any<>

David Waite david at alkaline-solutions.com
Thu May 19 00:51:36 CDT 2016

I’m a fan (mostly because I think it helps existential types, which have blocked quite a few library projects of mine), but I do have a few questions about the impact of the proposal

- I assume ‘Any' is still valid?
- In that case, would 'Any<>' be equivalent to ‘Any’, or a warning/error?
- What about 'Any<Any>' and such combinations?
- Does Any eventually become a keyword to deal with these sorts of special cases, the unbounded generic parameters, as well as future existential type uses (such as including a ‘where’ clause)?


> On May 18, 2016, at 11:35 PM, Austin Zheng via swift-evolution <swift-evolution at swift.org> wrote:
> Hello all,
> Swift 3.0 focuses on making breaking changes that prepare the way for features to be introduced in future releases. In that spirit, I would like to solicit feedback on a very simple proposal: renaming 'protocol<>' to 'Any<>', as described in the 'Completing Generics' manifesto.
> The proposal can be found here: https://github.com/austinzheng/swift-evolution/blob/az-protocol-to-any/proposals/XXXX-any-as-existential.md <https://github.com/austinzheng/swift-evolution/blob/az-protocol-to-any/proposals/XXXX-any-as-existential.md>
> Best,
> Austin
> _______________________________________________
> swift-evolution mailing list
> swift-evolution at swift.org
> https://lists.swift.org/mailman/listinfo/swift-evolution

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.swift.org/pipermail/swift-evolution/attachments/20160518/71e5dcab/attachment.html>

More information about the swift-evolution mailing list