<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class="">The where clause is not a stylistic flourish because it is still best used to constrain conditions that are semantically</div><div class="">related to conditions. Upon acceptance as now, there are no compiler checks that mandate any relationship. </div><div class=""><br class=""></div><div class="">The difference is that (1) coders will be allowed to move Boolean assertions out of where clauses when there is no</div><div class="">relationship, and (2) they will be allowed to order the statements as desired. Under the current system, all boolean</div><div class="">clauses must be conjoined and expressed as the first item of the list (except after availability clauses, as the one exception)</div><div class=""><br class=""></div><div class="">-- E</div><div class=""><br class=""></div><div><blockquote type="cite" class=""><div class="">On May 24, 2016, at 11:01 AM, Xiaodi Wu <<a href="mailto:xiaodi.wu@gmail.com" class="">xiaodi.wu@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class="">With the implementation of your proposal, will there be anything that can be written in where clauses that cannot be written after a comma (in the context of guard statements specifically)? If not, does the where clause become entirely a stylistic flourish?<br class=""><div class="gmail_quote"><div dir="ltr" class="">On Tue, May 24, 2016 at 11:57 Erica Sadun <<a href="mailto:erica@ericasadun.com" class="">erica@ericasadun.com</a>> wrote:<br class=""></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word" class=""><div class="">There is no way I could figure out how to restrict Boolean assertions to mentioned variables therefore I left where clauses entirely untouched.</div><div class="">I'd recommend people adopt in-house standards where Boolean assertions in where clauses should be semantically tied to the condition</div><div class="">clause that introduces them.</div><div class=""><br class=""></div><div class="">I will add this as a note.</div></div><div style="word-wrap:break-word" class=""><div class=""><br class=""></div><div class="">-- E</div></div><div style="word-wrap:break-word" class=""><div class=""><br class=""></div><br class=""><div class=""><blockquote type="cite" class=""><div class="">On May 24, 2016, at 9:29 AM, Xiaodi Wu <<a href="mailto:xiaodi.wu@gmail.com" target="_blank" class="">xiaodi.wu@gmail.com</a>> wrote:</div><br class=""><div class="">Does this proposal distinguish between "where clauses [...] restricted to a Boolean assertion tied to variables connected to the binding or pattern condition" and "unrelated Boolean assertions [that] should be allowed to stand on their own"?<br class=""><br class="">Or are both types of boolean assertions now permitted either following a comma or following a where clause?<br class=""></div></blockquote></div></div></blockquote></div></div></blockquote></div><br class=""></body></html>