Re: [swift-evolution] Allow trailing comma in guard, if-let, et al

> On Aug 19, 2016, at 10:26 , Karl Wagner wrote: > > Guard wouldn't work, because the "else" is usually on the same line as the > last element. Not in my coding style. > Perhaps the answer is better commenting in IDEs? So if you select a region > and hit CMD+/ Xcode will

Re: [swift-evolution] Allow trailing comma in guard, if-let, et al

Guard wouldn't work, because the "else" is usually on the same line as the last element. Perhaps the answer is better commenting in IDEs? So if you select a region and hit CMD+/ Xcode will comment with /*...*/ instead of sticking a // in front of the whole line. Perhaps it could

Re: [swift-evolution] Allow trailing comma in guard, if-let, et al

> On Aug 17, 2016, at 18:11 , Ben Rimmington wrote: > > >> On 18 Aug 2016, at 00:13, Rick Mann wrote: >> >> Is there any reason Swift can't allow a trailing comma in constructs like >> this: >> >> guard >> let a = ..., >> let b = ..., >> let c = ..., >> else >>

Re: [swift-evolution] Allow trailing comma in guard, if-let, et al

> On 18 Aug 2016, at 00:13, Rick Mann wrote: > > Is there any reason Swift can't allow a trailing comma in constructs like > this: > > guard >let a = ..., >let b = ..., >let c = ..., > else > { > } > > doing so makes it a bit easier to rearrange lines, and is similar to the >

[swift-evolution] Allow trailing comma in guard, if-let, et al

Is there any reason Swift can't allow a trailing comma in constructs like this: guard let a = ..., let b = ..., let c = ..., else { } doing so makes it a bit easier to rearrange lines, and is similar to the trailing comma allowed inside array and dictionary definitions: let a = [