<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="">-1<div class=""><br class=""><div><blockquote type="cite" class=""><div class="">Am 10.06.2016 um 21:10 schrieb Brent Royal-Gordon via swift-evolution <<a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a>>:</div><br class="Apple-interchange-newline"><div class=""><span style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;" class="">if case .some(let Point.cartesian(x, y)) where x < y = json["rect"]?["origin"].flatMap(.init(rawValue:)) { … }</span></div></blockquote><br class=""></div><div>This: `where x < y = json[…]` is *very* unreadable and probably unparseable as it is missing a delimiter between the boolean expression and the expression behind the assignment operator. And I do not count the assignment operator as a sufficient delimiter.</div><div><br class=""></div><div><br class=""></div><div>I’ll give the following counterargument against this shuffling around of `where` or trying to eliminate it:</div><div><br class=""></div><div><span class="Apple-tab-span" style="white-space:pre"> </span>if case .some(let x) = someExpression where x > 0</div><div><br class=""></div><div><span class="Apple-tab-span" style="white-space:pre"> </span>for x in xs where x > 0</div><div><br class=""></div><div>These are actually very consistent in their grammar when you look at it like follows:</div><div><br class=""></div><div><span class="Apple-tab-span" style="white-space:pre"> </span><target> <assignment op> <source> where <condition></div><div><br class=""></div><div><br class=""></div><div><span class="Apple-tab-span" style="white-space:pre"> </span>if case .some(let x) = someExpression where x > 0</div><div><br class=""></div><div><span class="Apple-tab-span" style="white-space:pre"> </span>target: `case .some(let x)`</div><div><span class="Apple-tab-span" style="white-space:pre"> </span>assignment op: `=`</div><div><span class="Apple-tab-span" style="white-space:pre"> </span>source: `someExpression`</div><div><span class="Apple-tab-span" style="white-space:pre"> </span>condition: `x > 0`</div><div><br class=""></div><div><br class=""></div><div><div><span class="Apple-tab-span" style="white-space: pre;"> </span>for x in xs where x > 0</div><div class=""><br class=""></div><div class=""><div><span class="Apple-tab-span" style="white-space: pre;"> </span>target: `x`</div><div><span class="Apple-tab-span" style="white-space: pre;"> </span>assignment op: `in`</div><div><span class="Apple-tab-span" style="white-space: pre;"> </span>source: `xs`</div><div><span class="Apple-tab-span" style="white-space: pre;"> </span>condition: `x > 0`</div></div><div class=""><br class=""></div><div class=""><br class=""></div><div class="">That is I’m arguing the `where` grammar is already quite regular and should not be changed. And yes, I’d like to have `where` back in `case`. And `let`.</div><div class=""><br class=""></div></div><div>-Thorsten</div><br class=""></div></body></html>