<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div>I've never really been able to read this naturally.</div><div id="AppleMailSignature">What opinions do people have on </div><div id="AppleMailSignature">{ with variable do sequence }</div><div id="AppleMailSignature">Or </div><div id="AppleMailSignature">with variable { sequences }</div><div id="AppleMailSignature"><br></div><div id="AppleMailSignature">ABR.</div><div><br>On 13 Dec 2015, at 15:03, Marc Knaup via swift-evolution <<a href="mailto:swift-evolution@swift.org">swift-evolution@swift.org</a>> wrote:<br><br></div><blockquote type="cite"><div><div dir="ltr"><div><div>Compare the following cases:<br></div><div><br></div><div><font face="monospace, monospace">#1</font></div><div><font face="monospace, monospace">for variable in sequence {}</font></div><div><font face="monospace, monospace"><br></font></div><div><font face="monospace, monospace">#2</font></div><div><font face="monospace, monospace">someFunction({ variable in sequence })</font></div><div><font face="monospace, monospace"><br></font></div><div><font face="arial, helvetica, sans-serif">Case #1 assigns elements from sequence to variable, so sequence is the SOURCE and variable is the DESTINATION.</font></div><div><font face="arial, helvetica, sans-serif">Case #2 has variable as SOURCE and sequence as DESTINATION (return value).</font></div><div><font face="arial, helvetica, sans-serif">It's flipped!</font></div><div><font face="arial, helvetica, sans-serif">It feels like it's meaning the same ("destination IN source") but it is not. That's inconsistent and confusing.</font></div></div><div><br></div><div>Changing #2 to the following breaks the inconsistency and avoids the confusion:</div><div><br></div><div><span style="font-family:monospace,monospace">someFunction({ variable do sequence })</span><br></div><div><br></div><div>I know the example doesn't make much sense as it just returns the sequence and ignores the variable. But it's good enough to highlight the inconsistency.</div><div><br></div><div class="gmail_extra"><br><div class="gmail_quote">On Sun, Dec 13, 2015 at 3:47 PM, Thorsten Seitz <span dir="ltr"><<a href="mailto:tseitz42@icloud.com" target="_blank">tseitz42@icloud.com</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"><span class=""><br><div><blockquote type="cite"><div>Am 13.12.2015 um 15:26 schrieb Marc Knaup <<a href="mailto:marc@knaup.koeln" target="_blank">marc@knaup.koeln</a>>:</div><br><div><div style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px">I agree though that "in" is confusing and I never understood what "in" means here.</div><div style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px">Since "do" is no longer used for loops but code blocks it would make sense to replace "in" with "do“. </div></div></blockquote><br></div></span><div>Well, I read</div><div><br></div><div>{ error <b>in</b> … }</div><div><br></div><div>as meaning, „error“ is bound within („in“) the following statements. I’m fine with that.</div><span class=""><font color="#888888"><div><br></div><div>-Thorsten</div></font></span></div></blockquote></div><br></div></div>
<img src="https://u2002410.ct.sendgrid.net/wf/open?upn=XyCJWhfMItFjSNmahITOc-2FRt7M7ZPPMxJlQpEnkvwDNys4UkhubER3mk937nJ8GT7XGsldGugpPWCd-2Bx0-2B4cgcHFnYc7yzGeXng-2FltHtqKYZskm4MsaLoZT41r44fYdR6oRVBTsajZUcvViLKNXwzyyTO6aaqOrr2uL-2FvGXNtCgQfYWIJlorNiuw838ysEeWqCztkKVLn-2BExIWvPagxzUw-3D-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;">
</div></blockquote><blockquote type="cite"><div><span>_______________________________________________</span><br><span>swift-evolution mailing list</span><br><span><a href="mailto:swift-evolution@swift.org">swift-evolution@swift.org</a></span><br><span><a href="https://lists.swift.org/mailman/listinfo/swift-evolution">https://lists.swift.org/mailman/listinfo/swift-evolution</a></span><br></div></blockquote></body></html>