[swift-evolution] [Proposal] Disallow redundant `Any<...>` constructs

Adrian Zubarev adrian.zubarev at devandartist.com
Fri May 20 10:19:27 CDT 2016

I don't understand what you mean.  I definitely think your 'typealias ABC = Any<AB, C>' should be valid.
I said typealias ABC = Any<AB, C> is valid.


typealias AliasA = Any<A>

is not and furthermore

typealias AliasAA = Any<AliasA>

should also not be valid because Any<Any<A>> shouldn’t be valid.

IMO the rules around banning nested any are unnecessary complexity.  The constructs have a well defined meaning.  The argument to ban them is purely around limiting allowable syntactic style.  People are very unlikely to actually use this nesting except through the abstraction of a typealias which is a very valid use case.  The complexity of the rules does not appear to provide any tangible benefit.

Which rule(s) do you refer to exactly?

Adrian Zubarev
Sent with Airmail

Am 20. Mai 2016 bei 17:12:40, Matthew Johnson (matthew at anandabits.com) schrieb:
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.swift.org/pipermail/swift-evolution/attachments/20160520/7cccee00/attachment.html>

More information about the swift-evolution mailing list