<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div><br></div><div><div>Regards<div>LM</div><div>(From mobile)</div></div>On Jun 24, 2016, at 5:55 AM, Jordan Rose via swift-evolution <<a href="mailto:swift-evolution@swift.org">swift-evolution@swift.org</a>> wrote:<br><br></div><blockquote type="cite"><div><meta http-equiv="Content-Type" content="text/html charset=utf-8"><div class="">[Proposal: <a href="https://github.com/apple/swift-evolution/blob/master/proposals/0095-any-as-existential.md" class="">https://github.com/apple/swift-evolution/blob/master/proposals/0095-any-as-existential.md</a> ]</div><div class=""><br class=""></div><div class="">I’ve gone on record before as against this syntax, although when I set out earlier today to record my usual rebuttal I found that it really was mostly a matter of taste. Yes, this looks weird to me:</div><div class=""><br class=""></div><blockquote style="margin: 0 0 0 40px; border: none; padding: 0px;" class=""><div class="">let callback: (Data) -> NSCoding & NSCopying</div></blockquote><div class=""><br class=""></div>but I’m sure the infix ‘->’ for functions looked weird to everyone the first time they saw it as well, and it really is pretty clear in argument position.<div class=""><br class=""></div><div class="">However, I did remember one issue, which was brought up on the previous mega-thread: if we do want to <a href="https://github.com/apple/swift/blob/master/docs/GenericsManifesto.md#generalized-existentials" class="">generalize protocol values</a>, we’re going to want something that’s essentially “a type with a ‘where’ clauses in it”. I really don’t want to force people to use a typealias to spell such a type, but at the same time I want that where clause to be clearly attached to the type. (As brought up before the return position of a function is currently ambiguous with <a href="https://github.com/apple/swift-evolution/blob/master/proposals/0081-move-where-expression.md" class="">SE-0081</a>.)</div><div class=""><br class=""></div><div class="">Despite the lightweightedness and the well-prepared proposal by Adrian and Austin, the lack of bracketing <> () {} [] leads me to maintain my stance against the proposed syntax.</div></div></blockquote><div><br></div><div>This is another way to generalize P&Q compositions that opens another way to specify WHERE</div><div><br></div><div><a href="https://gist.github.com/lmihalkovic/68c321ea7ffe27e553e37b794309b051">https://gist.github.com/lmihalkovic/68c321ea7ffe27e553e37b794309b051</a></div><br><blockquote type="cite"><div><div class=""><br class=""></div><div class="">Jordan<br class=""><div class=""><div class=""><br class=""></div></div></div></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></body></html>