<html><head><style>
body {
font-family: "Helvetica Neue", Helvetica, Arial, sans-serif;
padding:1em;
margin:auto;
background:#fefefe;
}
h1, h2, h3, h4, h5, h6 {
font-weight: bold;
}
h1 {
color: #000000;
font-size: 28pt;
}
h2 {
border-bottom: 1px solid #CCCCCC;
color: #000000;
font-size: 24px;
}
h3 {
font-size: 18px;
}
h4 {
font-size: 16px;
}
h5 {
font-size: 14px;
}
h6 {
color: #777777;
background-color: inherit;
font-size: 14px;
}
hr {
height: 0.2em;
border: 0;
color: #CCCCCC;
background-color: #CCCCCC;
display: inherit;
}
p, blockquote, ul, ol, dl, li, table, pre {
margin: 15px 0;
}
a, a:visited {
color: #4183C4;
background-color: inherit;
text-decoration: none;
}
#message {
border-radius: 6px;
border: 1px solid #ccc;
display:block;
width:100%;
height:60px;
margin:6px 0px;
}
button, #ws {
font-size: 12 pt;
padding: 4px 6px;
border-radius: 5px;
border: 1px solid #bbb;
background-color: #eee;
}
code, pre, #ws, #message {
font-family: Monaco;
font-size: 10pt;
border-radius: 3px;
background-color: #F8F8F8;
color: inherit;
}
code {
border: 1px solid #EAEAEA;
margin: 0 2px;
padding: 0 5px;
}
pre {
border: 1px solid #CCCCCC;
overflow: auto;
padding: 4px 8px;
}
pre > code {
border: 0;
margin: 0;
padding: 0;
}
#ws { background-color: #f8f8f8; }
.bloop_markdown table {
border-collapse: collapse;
font-family: Helvetica, arial, freesans, clean, sans-serif;
color: rgb(51, 51, 51);
font-size: 15px; line-height: 25px;
padding: 0; }
.bloop_markdown table tr {
border-top: 1px solid #cccccc;
background-color: white;
margin: 0;
padding: 0; }
.bloop_markdown table tr:nth-child(2n) {
background-color: #f8f8f8; }
.bloop_markdown table tr th {
font-weight: bold;
border: 1px solid #cccccc;
margin: 0;
padding: 6px 13px; }
.bloop_markdown table tr td {
border: 1px solid #cccccc;
margin: 0;
padding: 6px 13px; }
.bloop_markdown table tr th :first-child, table tr td :first-child {
margin-top: 0; }
.bloop_markdown table tr th :last-child, table tr td :last-child {
margin-bottom: 0; }
.bloop_markdown blockquote{
border-left: 4px solid #dddddd;
padding: 0 15px;
color: #777777; }
blockquote > :first-child {
margin-top: 0; }
blockquote > :last-child {
margin-bottom: 0; }
code, pre, #ws, #message {
word-break: normal;
word-wrap: normal;
}
hr {
display: inherit;
}
.bloop_markdown :first-child {
-webkit-margin-before: 0;
}
code, pre, #ws, #message {
font-family: Menlo, Consolas, Liberation Mono, Courier, monospace;
}
.send { color:#77bb77; }
.server { color:#7799bb; }
.error { color:#AA0000; }</style></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div class="bloop_markdown"><p>I like the decision of the core team to replace <code>protocol<…></code> with something like <code>&</code> instead. This gives us room to rethink <code>Any<…></code> or come up with even better mechanism for existentials. :)</p>
<p>There are still a few things to consider:</p>
<ul>
<li><code>AnyObject</code> and <code>AnyClass</code>:
<ul>
<li>I’d prefer to drop the current <code>AnyClass</code> and rename <code>AnyObject</code> to <code>AnyClass</code>, where the current <code>AnyClass</code> would be used as <code>AnyClass.Type</code>.</li>
<li><code>AnyClass & SomeProtocol</code> looks better to me than <code>AnyObject & SomeProtocol</code>.</li>
<li>What do you think?</li>
</ul></li>
<li>Would nesting for class-requirement work the same as we described before?</li>
</ul>
<p></p></div><div class="bloop_original_html"><style>body{font-family:Helvetica,Arial;font-size:13px}</style><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> <br> <div id="bloop_sign_1465024004515172864" 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 2. Juni 2016 um 17:25:54, Austin Zheng via swift-evolution (<a href="mailto:swift-evolution@swift.org">swift-evolution@swift.org</a>) schrieb:</p> <blockquote type="cite" class="clean_bq"><span><div><div></div><div>I'm sure the list is getting sick of me making this point over and<br>over again :), so I'll only do it one more time: I find the lack of<br>delimiters far worse in terms of readability for type expressions of<br>any appreciable complexity than any number of `Any<>` tokens. In fact,<br>I'm a bit surprised the core team decided to go in this direction,<br>given their stance on parentheses for function types, and replacing<br>operators like "&&" or "||" with "and" or "or". I respect their<br>decision, though.<br><br>On 6/2/16, Thorsten Seitz <tseitz42@icloud.com> wrote:<br>><br>><br>>> Am 02.06.2016 um 07:42 schrieb Austin Zheng via swift-evolution<br>>> <swift-evolution@swift.org>:<br>>><br>>> Excellent.<br>>><br>>> I put together a PR with a revised proposal containing the core team's<br>>> recommended approach. If anyone is curious they can see it here:<br>>> https://github.com/austinzheng/swift-evolution/blob/ef6adbe0fe09bff6c44c6aa9d73ee407629235ce/proposals/0095-any-as-existential.md<br>>><br>>> Since this is the de-facto second round discussion thread, I'll start with<br>>> my personal opinion (which is *not* reflected in the PR): the '&'<br>>> separators in lieu of commas are a good idea, but I would still prefer the<br>>> types to be wrapped in "Any<>", at least when being used as existentials.<br>><br>> I'm very happy with using `&` as I find this very readable.<br>> I would prefer not having to wrap them into `Any<>`. While I can image<br>> `Any<>`, or rather `any<>`, for existentials with `where` clauses, I would<br>> absolutely hate having to wrap all existentials into that which would<br>> introduce a lot of noise.<br>><br>>><br>>> My reasons:<br>>><br>>> - Jordan Rose brought up a good point in one of the discussion threads<br>>> today: a resilience goal is to allow a library to add an associated type<br>>> to a protocol that had none and not have it break user code. If this is<br>>> true whatever syntax is used for existentials in Swift 3 should be a valid<br>>> subset of the generalized existential syntax used to describe protocol<br>>> compositions with no associated types.<br>><br>> If `P` is an existential there is no problem either, isn't it? No need to<br>> require `Any<P>`.<br>><br>><br>><br>>><br>>> - I would rather have "Any<>" be used consistently across all existential<br>>> types eventually than have it only be used for (e.g.) existential types<br>>> with `where` constraints, or allowing two different representations of the<br>>> same existential type (one with Any, and one without).<br>><br>> Far too much noise!<br>><br>><br>>><br>>> - I think any generalized existential syntax without delimiting markers<br>>> (like angle braces) is harder to read than syntax with such markers, so I<br>>> would prefer a design with those markers.<br>><br>> I think markers are only needed if a `where` clause is present and probably<br>> not even then.<br>><br>> -Thorsten<br>><br>><br>>><br>>> Best,<br>>> Austin<br>>><br>>>>> On Jun 1, 2016, at 10:17 PM, Chris Lattner <clattner@apple.com> wrote:<br>>>>><br>>>>><br>>>>> On Jun 1, 2016, at 9:53 PM, Austin Zheng <austinzheng@gmail.com> wrote:<br>>>>><br>>>>> This was indeed a very thorough review by the core team. I'll prepare a<br>>>>> v2 proposal with this feedback taken into account so we can continue<br>>>>> moving things along.<br>>>>><br>>>>> One quick question - is making whatever syntax is chosen for Swift 3<br>>>>> "forward-compatible" with a future generalized existential feature a<br>>>>> concern?<br>>>><br>>>> Yes it is a concern, but we assume that the “X & Y” syntax will always be<br>>>> accepted going forward, as sugar for the more general feature that is yet<br>>>> to be designed.<br>>>><br>>>> -Chris<br>>><br>>> _______________________________________________<br>>> swift-evolution mailing list<br>>> swift-evolution@swift.org<br>>> https://lists.swift.org/mailman/listinfo/swift-evolution<br>><br>_______________________________________________<br>swift-evolution mailing list<br>swift-evolution@swift.org<br>https://lists.swift.org/mailman/listinfo/swift-evolution<br></div></div></span></blockquote></div><div class="bloop_markdown"><p></p></div></body></html>