-1 I think end-of-line semicolons are ugly. I also think the decision to use them or not use them should be left to individuals and not enforced by the compiler.
In the current implementation a semicolon can be optionally added after any statement and is proactively used to separate statements on a single line. Changing the language to enforce what appears to be a style choice is not something I'd support. The issue with the return needing a semicolon sounds odd to me. I'm curious as to whether that's something that needs fixing. -- E > On Mar 16, 2016, at 9:25 AM, Chris Wood via swift-evolution > <[email protected]> wrote: > > A word of warning on this - I’ve just hit a case where an end of line > semicolon is actually critical! > > If you’re debugging and need an early exit from a function, you add “return” > somewhere in the middle of the code. But return can take an argument, so the > compiler takes the argument from the following line which you think won’t be > executed. Bad things happen, followed by swearing. > > So in that particular case, you do in fact need to write: > > return; > > There may be other edge cases where it’s necessary to explicitly mark the end > of something in the same way. > > Chris Wood > > >> Hi, >> >> I submitted a PR with a proposal to remove the swift end of line semicolons. >> >> It was rejected because i didn't discuss it here. So here i'm discussing it >> :) >> >> My proposal is simple: remove the semicolons in the end of lines. >> It isn't needed and makes the code ugly. >> It must be decided wether to use it or not for every project we start in the >> coding style. >> >> What do you think? >> >> João Nunes >> >> >> Sent from my iPhone >> >> >> > > _______________________________________________ > swift-evolution mailing list > [email protected] > https://lists.swift.org/mailman/listinfo/swift-evolution _______________________________________________ swift-evolution mailing list [email protected] https://lists.swift.org/mailman/listinfo/swift-evolution
