[swift-evolution] [Pitch] merge types and protocols back together with type<Type, Protocol, ...>
tseitz42 at icloud.com
Tue May 17 00:17:14 CDT 2016
But don't you mean the union type of all possible Collection types when you write Any<Collection>?
I suggested `all<>` for the intersection type, and `any<>` for the union type, so that would be the same, wouldn't it?
Am 17.05.2016 um 07:10 schrieb Brent Royal-Gordon via swift-evolution <swift-evolution at swift.org>:
>> We've been over this a few times before on the list. I personally like naming this thing "Any<…>" in the same vein as "AnyObject", "AnyClass", and "AnySequence". I also see Thorsten (and in the past Brent's?) argument for calling it "all" or "All", because it's enforcing multiple constraints.
> I have suggested `all<>` in the past, but I now favor `Any`, because that allows it to be unified with the universal supertype `Any`, `Any<class>`, and things like `Any<Collection>` to forge the One Existential Syntax to rule them all.
> Brent Royal-Gordon
> swift-evolution mailing list
> swift-evolution at swift.org
More information about the swift-evolution