<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">These are some very interesting ideas to explore. I definitely want to play with the bar character as a separator. This could nicely deal with the problem of the double colon in the hybrid approach. <div class=""><br class=""></div><div class="">I like this thinking as it really explores a different approach.It is cool the way it can be lined up like that and it reads well when you think of the bar as “when”. I am a little concerned that some may be considered weird but not better than the ternary, which is some of the feedback I got from my earlier designs. I suppose if we are making a breaking change though, that may be okay but keep in mind it there should be a reason for making it different. This suggestion definitely has a different feel than the existing ternary. How do people feel about that?</div><div class=""><br class=""></div><div class="">I also agree, I am not sure how that would work for expressions.</div><div class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Dec 22, 2015, at 7:36 AM, Matthew Johnson via swift-evolution <<a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><meta http-equiv="content-type" content="text/html; charset=utf-8" class=""><div dir="auto" class=""><div class="">This looks reasonable in declarations but how would it work in expressions? Or are you suggesting that it is only usable for declarations?<br class=""><br class="">Sent from my iPad</div><div class=""><br class="">On Dec 22, 2015, at 9:25 AM, Angelo Villegas via swift-evolution <<a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a>> wrote:<br class=""><br class=""></div><blockquote type="cite" class=""><div class="">I for one feels like the ternary operator still has a future with Swift.<br class=""><br class="">If the discussion with ternary will go on though, I would like to weigh in a suggestion:<br class=""><br class=""><font face="Courier" class=""> let a | x == y = a<br class=""> | otherwise = b<br class=""><br class=""> let b | colour.Red = 0xff0000</font><div class=""><font face="Courier" class=""> | colour.Green = 0x00ff00</font></div><div class=""><font face="Courier" class=""> | colour.Blue = 0x0000ff</font></div><div class=""><font face="Courier" class=""> | otherwise = 0x000000<br class=""></font><br class="">My rule of thumb for a style like this is that if you can read it as if it was English (read | (bar) as "when", | otherwise (bar otherwise) as "otherwise" and = as "is" or "be"), you're probably doing something right.</div>
<img src="https://u2002410.ct.sendgrid.net/wf/open?upn=eLFMrKDT8iBxZ-2Fbnk-2BZqvSchNN-2FvYXdceA0T7VxwkAf-2FkSH9aYxDJfUmY8VbF2oU8sTslmlZ9SrpFQHwEhEO-2Fe16odmfHIQRw8oHEhBYWBNkqoRnjh3dNbBPCFybCy9ukXzKdh1yJML-2BJo8BPtrmbigF8-2FqWxjHgvrpyPU9boRSGE6ohWQuXDo4WN5iVAs3dk0vjsRHsj96DKCZuIyn3mRy6tVL12UONamWDMCaC4nQ-3D" alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;" class="">
</div></blockquote><blockquote type="cite" class=""><div class=""><span class="">_______________________________________________</span><br class=""><span class="">swift-evolution mailing list</span><br class=""><span class=""><a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a></span><br class=""><span class=""><a href="https://lists.swift.org/mailman/listinfo/swift-evolution" class="">https://lists.swift.org/mailman/listinfo/swift-evolution</a></span><br class=""></div></blockquote>
<img src="https://u2002410.ct.sendgrid.net/wf/open?upn=emrIhnP1hIf76Foxxv4NNJQX-2FWhcznESwKBSwD1MEwyLa7SHQVRRj7PqqvMWAoU523l9joKsWA55K5xTM5E45A-2FAOp-2FvtlxkhRdZxOM8z1Er4uLfDYGaSp4cEf1cocLd3sc3t38Bjk1AZpZP-2BfDrzA8YsLipU1V9mEhae3pr-2BrUl18xqXFEKK6VmPDXlTc6vQNOxWUJfhjZ4KN4Ww8i4KGZHDaAvy4YzsIWgrI2i6cc-3D" alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;" class="">
</div>
_______________________________________________<br class="">swift-evolution mailing list<br class=""><a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a><br class="">https://lists.swift.org/mailman/listinfo/swift-evolution<br class=""></div></blockquote></div><br class=""></div></body></html>