<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=""><div class="">+1 to “better handled by a linter.” As with the “required self.” proposal, this seems better suited to an external style checker than to a language rule.</div><div class=""><br class=""></div><div class=""><div class="">SwiftLint can already generate warnings and errors that look exactly like compiler errors in Xcode for those who want the seamlessness of a language rule.</div><div class=""><br class=""></div></div><div class="">If the language provides a construct, there are always unforeseen consequences to not providing it in its full generality, even when good style dictates narrower usage. For example: this proposal might complicate Swift code generation. I know, code generation, who wants that, yuck, right? But there are time when it’s the right solution, and being able to just concatenate things with terminating semicolons and not have worry about an arbitrary EOL rule would make a generator’s job easier.</div><div class=""><br class=""></div><div class="">Cheers, P</div><br class=""><div><blockquote type="cite" class=""><div class="">On Dec 14, 2015, at 12:04 PM, Arthur Ariel Sabintsev via swift-evolution <<a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class="">I'm also game for making them invalid syntax. <div class=""><br class=""></div><div class="">The only time I've seen `;` in my code is from my old Obj-C habit.</div></div><br class=""><div class="gmail_quote"><div dir="ltr" class="">On Mon, Dec 14, 2015 at 12:25 PM Austin Zheng via swift-evolution <<a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a>> wrote:<br class=""></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Semicolons are already optional at the end of lines and only required to separate multiple statements on the same line (and for C for loops, but changing the grammar of those or removing them is a different topic.<br class="">
<br class="">
If your proposal is to make a semicolon at the end of a single line invalid syntax, that's fine with me, although it seems like an unnecessarily small change to the grammar (and something better handled by a linter). If your proposal is to remove the semicolon as a way to separate multiple statements on the single line, then -1.<br class="">
<br class="">
Austin<br class="">
<br class="">
> On Dec 13, 2015, at 6:12 AM, João Nunes via swift-evolution <<a href="mailto:swift-evolution@swift.org" target="_blank" class="">swift-evolution@swift.org</a>> wrote:<br class="">
><br class="">
> Hi,<br class="">
><br class="">
> I submitted a PR with a proposal to remove the swift end of line semicolons.<br class="">
><br class="">
> It was rejected because i didn't discuss it here. So here i'm discussing it :)<br class="">
><br class="">
> My proposal is simple: remove the semicolons in the end of lines.<br class="">
> It isn't needed and makes the code ugly.<br class="">
> It must be decided wether to use it or not for every project we start in the coding style.<br class="">
><br class="">
> What do you think?<br class="">
><br class="">
> João Nunes<br class="">
><br class="">
><br class="">
> Sent from my iPhone<br class="">
> _______________________________________________<br class="">
> swift-evolution mailing list<br class="">
> <a href="mailto:swift-evolution@swift.org" target="_blank" class="">swift-evolution@swift.org</a><br class="">
> <a href="https://lists.swift.org/mailman/listinfo/swift-evolution" rel="noreferrer" target="_blank" class="">https://lists.swift.org/mailman/listinfo/swift-evolution</a><br class="">
<br class="">
_______________________________________________<br class="">
swift-evolution mailing list<br class="">
<a href="mailto:swift-evolution@swift.org" target="_blank" class="">swift-evolution@swift.org</a><br class="">
<a href="https://lists.swift.org/mailman/listinfo/swift-evolution" rel="noreferrer" target="_blank" class="">https://lists.swift.org/mailman/listinfo/swift-evolution</a><br class="">
</blockquote></div><div dir="ltr" class="">-- <br class=""></div><div dir="ltr" class="">Best,<div class=""><br class=""></div><div class="">Arthur / <a href="http://sabintsev.com" class="">Sabintsev.com</a></div></div>
<img src="https://u2002410.ct.sendgrid.net/wf/open?upn=zCg-2FSGF9Wk188a6c55kLyEbrj7YhaXxFEHM-2F-2B0YAlzXNXw8BKz-2FSEpcM-2FhPdtdd-2B2tbi3tzg3wy3G9p5RGGpqRC-2Big7mfJ500-2BwuNye0Wtb7lgdKyw-2BVwPQoJz5hdjlNDTtNUJSVG4dNWgYAx2wFOKZXAD-2BvjeBm-2BLwCEwJSl3CdEG5RZ7uofC2oMhTGlR8JAbNw5iQ1QrOaTY7DyMUQAvRyKtxapV5EAnup6ptECHU-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;" class="">
_______________________________________________<br class="">swift-evolution mailing list<br class=""><a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a><br class="">https://lists.swift.org/mailman/listinfo/swift-evolution<br class=""></div></blockquote></div><br class=""></body></html>