<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="">On Jun 24, 2016, at 2:53 PM, Xiaodi Wu <<a href="mailto:xiaodi.wu@gmail.com" class="">xiaodi.wu@gmail.com</a>> wrote:<br class=""><div><blockquote type="cite" class=""><br class="Apple-interchange-newline"><div class=""><span style="font-family: HelveticaNeue; 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="">The point I was trying to bring up was that a purported advantage of keeping `where` is moot for those who *do* observe line limits, which includes the Swift stdlib itself as well as (IIUC) house style at Google, Microsoft, etc.</span></div></blockquote></div><br class=""><div class="">Sorry, I wasn’t clear. I wasn’t saying that having it on the same exactly physical line is cleaner, I was saying that having the criteria for the “what I’m iterating” above the loop body and “what I’m doing with those things” inside the loop body is a much cleaner metaphor to me, and one of my favorite bits of Swift. It feels very Swifty to allow the programmer to separate these two concepts nicely.</div><div class=""><br class=""></div><div class="">I don’t care if/how lines are wrapped. In some cases I put the “where” on the next line in my code right now.</div><div class=""><br class=""></div><div class="">-Wil</div></body></html>