<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div>Thanks for all replies.</div><div id="AppleMailSignature"><br></div><div id="AppleMailSignature">This is helpful for introduce why for in be that for in other peoples.<br><br>나의 iPhone에서 보냄</div><div><br>2017. 7. 29. 05:14 Taylor Swift <<a href="mailto:kelvin13ma@gmail.com">kelvin13ma@gmail.com</a>> 작성:<br><br></div><blockquote type="cite"><div><div dir="ltr">This is funny because this “expected behavior” is actually a heavily criticized part of C behavior. I think this change would cause just as much if not more confusion than it alleviates.<br></div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Jul 28, 2017 at 12:19 PM, Kwanghoon Choi 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:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hello<br>
<br>
I found someone easy mistake using for in loop statement.<br>
<br>
Ex)<br>
var i = 0<br>
for i in 0..<10 { }<br>
print(i)<br>
<br>
And this user expected print(i) is “10”<br>
<br>
Many experienced swift developers doesn’t misunderstand like this. But always someone is new comers, and I think this expression make misunderstand easy too.<br>
<br>
So why not like this?<br>
<br>
var I = 0<br>
for 0..<10 { (i) in … }<br>
<br>
I think this is more understandable for loop expression.<br>
<br>
Best Regards<br>
<br>
- Jay Choi<br>
______________________________<wbr>_________________<br>
swift-evolution mailing list<br>
<a href="mailto:swift-evolution@swift.org">swift-evolution@swift.org</a><br>
<a href="https://lists.swift.org/mailman/listinfo/swift-evolution" rel="noreferrer" target="_blank">https://lists.swift.org/<wbr>mailman/listinfo/swift-<wbr>evolution</a><br>
</blockquote></div><br></div>
</div></blockquote></body></html>