<div dir="ltr">Hi all,<div><br><div>I'm a little bit surprised that this discussion has lost track of the idea of turning "switch" into an expression rather than a control-flow statement. Chris has expressed that he and other team members would like to consider this.<br></div><div><br></div><div>It was discussed a bit on the original version of this thread:</div><div><a href="https://lists.swift.org/pipermail/swift-evolution/2015-December/000385.html">https://lists.swift.org/pipermail/swift-evolution/2015-December/000385.html</a></div><div><br></div><div class="gmail_extra">And in "Control Flow Expressions":</div><div class="gmail_extra"><a href="https://lists.swift.org/pipermail/swift-evolution/2015-December/000393.html">https://lists.swift.org/pipermail/swift-evolution/2015-December/000393.html</a><br></div><div class="gmail_extra"><br></div><div class="gmail_extra">I've seen this ternary-operator discussion branching out in various directions and yet it slowly seems to converge back on "make it as similar to the existing switch statement as possible".</div><div class="gmail_extra"><br></div><div class="gmail_extra">Was switch-as-an-expression intentionally dropped from consideration, in favor of adding new syntax? If so, I may have missed that piece of the discussion, and would appreciate if someone could point me to it.</div><div class="gmail_extra"><br></div><div class="gmail_extra">Thanks,</div><div class="gmail_extra"><div><div><div dir="ltr"><div>Jacob<br></div></div></div></div>
<br><div class="gmail_quote">On Sun, Jan 17, 2016 at 4:08 PM, Craig Cruden via swift-evolution <span dir="ltr"><<a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div style="word-wrap:break-word">Another attempt on motivation to thread the needle.<div><br></div><div><a href="https://github.com/cacruden/swift-evolution/blob/master/proposals/0000-Pattern-Matching-Partial-Function.md" target="_blank">https://github.com/cacruden/swift-evolution/blob/master/proposals/0000-Pattern-Matching-Partial-Function.md</a></div><div><div><div><br><div><blockquote type="cite"><div>On 2016-01-18, at 3:04:35, Charles Constant <<a href="mailto:charles@charlesism.com" target="_blank">charles@charlesism.com</a>> wrote:</div><br><div><div dir="ltr"><div class="gmail_extra">I think examples are convincing, but ideally we would put most of them in separate document. </div><div class="gmail_extra"><br></div><div class="gmail_extra">Though I love reading about programming, I generally do it in a half-assed sort of way. Unless the writing is very blunt and clear, I don't really understand it until I need to do it myself. I doubt I'm the only person here like this. <br></div><div class="gmail_extra"><br></div><div class="gmail_extra">I badly want this proposal to gain traction (more so every time I find myself writing code that it could improve, which happens daily). I think the proposal ought to be short and sweet. I believe if we hold the reader's attention just long enough for them to understand what we're talking about, they'll be onboard. Once they're hooked, we have our second document with the list of examples.</div><div class="gmail_extra"><br></div><div class="gmail_extra">It would also be great to have the "before snippet" and "after snippet" visually arranged side-by-side. I'm guessing markdown doesn't support this :(</div><div class="gmail_extra"><br></div><div class="gmail_extra"><br></div></div>
</div></blockquote></div><br></div></div></div></div><br>_______________________________________________<br>
swift-evolution mailing list<br>
<a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a><br>
<a href="https://lists.swift.org/mailman/listinfo/swift-evolution" rel="noreferrer" target="_blank">https://lists.swift.org/mailman/listinfo/swift-evolution</a><br>
<br></blockquote></div><br></div></div></div>