+1 for this feature.
I don't see any problem with it, just like we all don't see any problem
with optional semicolon for code lines.
But I don't know if it will be possible(not too hard) to implement.
On 17.05.2016 21:06, Tino Heth wrote:
[Due to popular demand ;-) in the discussion of SE-0084: Allow trailing
commas in parameter lists and tuples]
The option to skip semicolons for statements followed by a newline is only
a tiny convinience, yet it is one of the most favored differences to C (and
one of the most annoying things to remember when you have to switch from
Swift to do some coding in Objective-C).
While lists of statements don't need a special separator character anymore,
other lists still rely on commas to separate items:
- method parameters
- array and dictionary literals
- tuples
[anything else?]
SE-0084 targets to make it easier to reorder list elements by allowing an
additional comma after the last element; afaics, the same can be achieved
by making all of those commas optional, as long as there is a newline to
separate the next item (without those newlines, SE-0084 makes less sense as
well).
This change is not incompatible with SE-0084, but imho it doesn't make much
sense to combine those features (at least in actual source code).
So, first question:
What are the downsides of this change? (question zero is "are there any
other places where comma-separeted lists could be turned into
newline-separated lists?"...)
Tino
_______________________________________________
swift-evolution mailing list
[email protected]
https://lists.swift.org/mailman/listinfo/swift-evolution
