<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;">If anyone is interested, I started a draft proposal with detailed design here: <a href="https://github.com/DevAndArtist/swift-evolution/blob/master/proposals/nnnn-merging-types-with-protocols.md">https://github.com/DevAndArtist/swift-evolution/blob/master/proposals/nnnn-merging-types-with-protocols.md</a></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 didn’t post it here, because it is a bit huge and could lose its markdown formats. `all<>` is always bold, because this is what we are interested in, but I provided all possible combinations if the other formats would exists (at least all combinations I could think of, anything else is derived from these). </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;">`class<>` etc. can be seen as a future direction (I would say), otherwise this would easily become out of scope for Swift 3. (I will move `class<>` etc. from detailed design to future direction later.)</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 love to hear your feedback and strong arguments for the motivation part I could include into this proposal.</div> <br> <div id="bloop_sign_1463182837742214912" 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 13. Mai 2016 bei 23:16:20, Vladimir.S (<a href="mailto:svabox@gmail.com">svabox@gmail.com</a>) schrieb:</p> <blockquote type="cite" class="clean_bq"><span><div><div></div><div>You asked for any example, I give it to you ;-)
<br>(as I said, it is syntactical, just to show that such struct<> can be used
<br>to test some struct for conforming to protocol, that was not conformed at
<br>writing time)
<br>Probably we can invent useful examples for this struct<> - but I don't
<br>believe it will be introduced in Swift ;-)
<br>
<br>On 13.05.2016 22:14, Adrian Zubarev via swift-evolution wrote:
<br>> Can we really do that? I mean, I thought about that myself but I came to
<br>> the conclusion that this scenario is like: I was to lazy to couple this
<br>> structs to my library protocols, will you do that for me?
<br></div></div></span></blockquote></body></html>