<html><head><style>body{font-family:Helvetica,Arial;font-size:13px}</style></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px; color: rgba(0,0,0,1.0); margin: 0px; line-height: auto;">So basically everyone start to like by the core team suggested `Any<>` name of the proposed mechanism. I’ll rename it when I get home. ;)</div><div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px; color: rgba(0,0,0,1.0); margin: 0px; line-height: auto;"><br></div><div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px; color: rgba(0,0,0,1.0); margin: 0px; line-height: auto;"><div><blockquote type="cite" class="clean_bq" style="font-family: Helvetica, Arial; font-size: 13px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;"><div dir="auto">I don't think Either is a good name. That implies 2 cases (either this or that). Maybe 'OneOf' would be better.</div></blockquote></div><p>Since that might be or be not a different proposal some day I guess we’d be safe to call it `OneOf` for the time being.</p></div><div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px; color: rgba(0,0,0,1.0); margin: 0px; line-height: auto;">Would you mind to go over the rules I suggested? Do we need the ability to provide multiple reference/value types? I’d say no we don’t, to reduce confusion (see my proposal).</div><div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px; color: rgba(0,0,0,1.0); margin: 0px; line-height: auto;"><br></div><div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px; color: rgba(0,0,0,1.0); margin: 0px; line-height: auto;">https://github.com/DevAndArtist/swift-evolution/blob/master/proposals/nnnn-mechanism-to-combine-types-and-protocols.md</div> <br> <div id="bloop_sign_1463492130063627008" class="bloop_sign"><div style="font-family:helvetica,arial;font-size:13px">-- <br>Adrian Zubarev<br>Sent with Airmail</div></div> <br><p class="airmail_on">Am 17. Mai 2016 bei 15:34:10, Matthew Johnson (<a href="mailto:matthew@anandabits.com">matthew@anandabits.com</a>) schrieb:</p> <blockquote type="cite" class="clean_bq"><span><div dir="auto"><div></div><div>
<title></title>
<div><br>
<br>
Sent from my iPad</div>
<div><br>
On May 17, 2016, at 5:12 AM, Adrian Zubarev via swift-evolution
<<a href="mailto:swift-evolution@swift.org">swift-evolution@swift.org</a>>
wrote:<br>
<br></div>
<blockquote type="cite">
<div>
<div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px; color: rgba(0,0,0,1.0); margin: 0px; line-height: auto;">
<div>
<blockquote type="cite" class="clean_bq" style="font-family: Helvetica, Arial; font-size: 13px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;">
<span style="font-family: 'helvetica Neue', helvetica;">But don't
you mean the union type of all possible Collection types when you
write Any<Collection>?</span><br style="font-family: 'helvetica Neue', helvetica;">
<br style="font-family: 'helvetica Neue', helvetica;">
<span style="font-family: 'helvetica Neue', helvetica;">I suggested
`all<>` for the intersection type, and `any<>` for the
union type, so that would be the same, wouldn't
it?</span></blockquote>
</div>
<p>Thats exactly how I understand out situation by now. I was
confused by Thorsten's `intersection` first, but now I see that he
meant the intersection between dynamic type and the whole set of
constraints provided by `All<…>`. I thought about about the
constraints union compared to the dynamic type, which is most
likely the same thing.</p>
<p>In my proposal I reserved the name `Any<>` for future
directions, but noted that we still might choose `Any<…>` for
the proposed `All<…>` and then name `Any<…>` described
by Thorsten as `Either<…>`.</p>
</div>
</div>
</blockquote>
<div><br></div>
<div>I agree with Brent's concept of Any. That feels Swifty,
following the convention established by the type-erasing wrappers
currently in the standard library. </div>
<div><br></div>
I don't think Either is a good name. That implies 2 cases
(either this or that). Maybe 'OneOf' would be better.
<div>
<blockquote type="cite">
<div>
<div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px; color: rgba(0,0,0,1.0); margin: 0px; line-height: auto;">
<div><br></div>
<div>
<blockquote type="cite" class="clean_bq" style="font-family: Helvetica, Arial; font-size: 13px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;">
<span style="font-family: 'helvetica Neue', helvetica;">>> 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.</span></blockquote>
</div>
<div>
<div>
<blockquote type="cite" class="clean_bq" style="font-family: Helvetica, Arial; font-size: 13px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;">
<span style="font-family: 'helvetica Neue', helvetica;">> </span><br style="font-family: 'helvetica Neue', helvetica;">
<span style="font-family: 'helvetica Neue', helvetica;">> 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.</span></blockquote>
</div>
<p>I considered `Any<>` as an alternative and personally I
don’t have anything against that little change. I still don’t like
`AnyObject` because it uses `Object` instead of `Class`, where
`AnyClass` is `AnyObject.Type`. This is way to confusing if you ask
me. I’d rename both into `ClassInstance` == `AnyObject` and
`ClassType` == `AnyClass`. If Swift one day might introduce
`struct` and `enum` keywords that are generalized like `class`
(could be) what name would you choose? Compared to `AnyClass`
typealias `AnyStruct` would be `AnyXYZ.Type`. The only type I like
which uses `Any` as its prefix is `Any` itself. </p>
<p>But I guess this is something the core team will decide.</p>
<p>If there is no feedback towards the document I wrote anymore,
I’ll submit a pull request later this day. (Note: I’ll add some
small changes in the alternatives section about dropping the
restriction of a single reference/value type within the angle
brackets).</p>
</div>
</div>
<div id="bloop_sign_1463463932242403072" class="bloop_sign">
<div style="font-family:helvetica,arial;font-size:13px">
-- <br>
Adrian Zubarev<br>
Sent with Airmail</div>
</div>
<br>
<p class="airmail_on">Am 17. Mai 2016 bei 07:17:21, Thorsten Seitz
via swift-evolution (<a href="mailto:swift-evolution@swift.org">swift-evolution@swift.org</a>)
schrieb:</p>
</div>
</blockquote>
<blockquote type="cite">
<div>
<span>_______________________________________________</span><br>
<span>swift-evolution mailing list</span><br>
<span><a href="mailto:swift-evolution@swift.org">swift-evolution@swift.org</a></span><br>
<span><a href="https://lists.swift.org/mailman/listinfo/swift-evolution">https://lists.swift.org/mailman/listinfo/swift-evolution</a></span><br>
</div>
</blockquote>
</div>
</div></div></span></blockquote></body></html>