Sent from my iPad
> On May 27, 2016, at 7:22 PM, Erica Sadun <[email protected]> wrote: > > >> On May 27, 2016, at 6:19 PM, Matthew Johnson <[email protected]> wrote: >>>> Also, can someone refer me to an example of this statement: "This proposal >>>> resolves this problem by retaining commas as separators within clauses (as >>>> used elsewhere in Swift) and introducing semicolons to separate distinct >>>> kinds of clauses (which aligns with the rest of the Swift language)” >>> >>> guard let x = opt1, y = opt2, z = opt3; booleanAssertion else { } >>> >>>> >>>> I rarely see any semicolons after the removal of C loops. So if someone >>>> could put me to where this is used elsewhere in Swift, please do! >>> >>> Using semicolons brings conditions in-line with how semicolons are used as >>> separators elsewhere in the Swift grammar. >> >> Not really. We can use a newline instead of the semicolon elsewhere. > > Outside of braces? Think of the guard/if/while creating a new miniscope that > has no braces, and whose value assignments escape to the surrounding scope. I > defer to Chris for better technical answers. They are only used for statement separators as far as I know. Statements only happen inside code blocks, which are always surrounded by braces. So no, not outside braces as far as I know. But I don't know what that has to do with the fact that newline can be used as an alternative. It's just an alternate separator. As far as I know, everywhere semicolons are used as separators newlines are accepted as an alternate separator. > > -- E >
_______________________________________________ swift-evolution mailing list [email protected] https://lists.swift.org/mailman/listinfo/swift-evolution
