# SE-0257: Eliding commas from multiline expression lists **URL:** \ **Category:** Proposal Reviews\ **Created:** [April 9, 2019, 11:46pm UTC](https://forums.swift.org/t/se-0257-eliding-commas-from-multiline-expression-lists/22889 "2019-04-09T23:46:33Z")\ **Posts on this page:** 1\ **Showing post:** 91
**Author:** ![jarod](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/jarod/32/364_2.png) [@jarod](https://forums.swift.org/u/jarod)\ **Post date:** [April 10, 2019, 11:29pm UTC](https://forums.swift.org/t/se-0257-eliding-commas-from-multiline-expression-lists/22889/91 "2019-04-10T23:29:42Z")
> [@Chris\_Lattner3](#): > > I also find it surprising and deeply concerning that we are considering a wide range of syntactic sugar proposals that are trivial syntax micro optimizations (eliding a single return keyword, eliding syntactically light-weight separators) that do not actual affect the clarity of code, or improve higher level expressivity of the language. There is a recent blossoming of syntactic sugar proposals on the list of similar ilk, and there are far bigger fish to fry. This is a really concerning to me direction to see the community take. I don't think this is totally fair — I disagree that two syntactic refinement proposals constitutes a wide range. [Bigger](https://forums.swift.org/t/se-0244-opaque-result-types-reopened/22942) [fish](https://forums.swift.org/t/improving-the-ui-of-generics/22814) are in fact still [being](https://forums.swift.org/t/se-0253-static-callables/22243) [fried](https://forums.swift.org/t/pitch-2-property-delegates-by-custom-attributes/22855), and I see no reason that we shouldn't make a small amount of room for small refinements like this. There will always be bigger problems to address than syntax refinement, but by that logic there will never be a time to address these issues. --- _[View the full topic](https://forums.swift.org/t/se-0257-eliding-commas-from-multiline-expression-lists/22889)._