<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;">Ok I feel like I’m ready to submit this `base` proposal for `Any<>` which can be extended even further later on.</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;">Please take a last look: https://github.com/DevAndArtist/swift-evolution/blob/master/proposals/nnnn-mechanism-to-combine-types-and-protocols.md</div> <br> <div id="bloop_sign_1463511654810321920" 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 20:18:55, Adrian Zubarev (<a href="mailto:adrian.zubarev@devandartist.com">adrian.zubarev@devandartist.com</a>) schrieb:</p> <blockquote type="cite" class="clean_bq"><span><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div></div><div>
<title></title>
<div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px; color: rgba(0,0,0,1.0); margin: 0px; line-height: auto;">
I really would like to understand what you was trying to tell me.
:) My English is a little rusty to understand every piece of
someone's thought.</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;">
By any chance someone could propose your ideas as an
enhancement/upgrade of my `Any<>` mechanism later on? I mean
like Joe did with removing `.self` which implies the ability
of parsing expressions after 'as' and 'is' instead of just
types.</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;">
I’d update my document soon at let you guys have a quick look over
it before I’ll submit a pull request. :)</div>
<br>
<div id="bloop_sign_1463508370431470848" 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 20:02:35, Douglas Gregor
(<a href="mailto:dgregor@apple.com">dgregor@apple.com</a>)
schrieb:</p>
<blockquote type="cite" class="clean_bq">
<div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">
<div><span><br class=""></span>
<div>
<blockquote type="cite" class="">
<div class=""><span>On May 17, 2016, at 10:40 AM, Adrian Zubarev
<<a href="mailto:adrian.zubarev@devandartist.com" class="">adrian.zubarev@devandartist.com</a>> wrote:</span></div>
<span><br class="Apple-interchange-newline"></span>
<div class="">
<div id="bloop_customfont" 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; margin: 0px;" class="">
<blockquote type="cite" class="clean_bq">
<div class="" style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">
<div class=""><span>You don’t seem to be tackling the case of “A
Collection whose Element type is String”. If we’re generalizing the
current “protocol<>” notion, why not make it as powerful as a
generic signature, with the ability to specify same-type
constraints and conformances on associated types?</span></div>
<div class=""><span><br class=""></span></div>
<span>- Doug</span></div>
</blockquote>
<div class="">
<div class="" style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">
<span><br class=""></span></div>
</div>
<div class="" style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">
<span>Which part of the manifesto did I left out? ^^ Could you
provide a quick pseudo code example?</span></div>
<div class="" style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">
<span><br class=""></span></div>
<div class="" style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">
<span>Do you mean something like `Any<Collection where Element
== String>`? I’m not sure where I should consider such a
scenario, maybe at future directions?</span></div>
</div>
</div>
</blockquote>
<div><span><br class=""></span></div>
<div><span>That’s the part I’m referring to, yes. I just realized
that your proposal isn’t lifting the restrictions on protocols with
Self types or associated types, so my suggestion doesn’t make sense
for your proposal without a significant increase in
scope.</span></div>
<div><span><br class=""></span></div>
<div><span>- Doug</span></div>
<div><span><br class=""></span></div>
</div>
</div>
</div>
</blockquote>
</div></div></span></blockquote></body></html>