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)? -DW > On May 18, 2016, at 11:35 PM, Austin Zheng via swift-evolution > <[email protected]> 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 > [email protected] > https://lists.swift.org/mailman/listinfo/swift-evolution
_______________________________________________ swift-evolution mailing list [email protected] https://lists.swift.org/mailman/listinfo/swift-evolution
