<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class=""><font color="#7c2a00" class=""><br class=""></font></div><div class=""><div class="" style="margin-top: 0px; margin-bottom: 0px;"><span class="s1"><font class="" color="#7c2a00">I will like to suggest the alternative </font></span></div><div class="" style="margin-top: 0px; margin-bottom: 0px;"><span class="s1"><font class="" color="#7c2a00">that consists in eliminating the use of "," since the compiler is able to know here they are expected, automatic watermarks can be added by Xcode to indicate where the compiler is automatically adding the comas. </font></span></div><div class="" style="margin-top: 0px; margin-bottom: 0px;"><span class="s1"><font class="" color="#7c2a00">also use of a “..” watermark at the end of a line will indicate that it continues on the next line, it will also be added on the start of the next line as well.</font></span></div><div class="" style="margin-top: 0px; margin-bottom: 0px;"><span class="s1"><font class="" color="#7c2a00"><br class=""></font></span></div><div class="" style="margin-top: 0px; margin-bottom: 0px;"><span class="s1"><font class="" color="#7c2a00">Optionally watermark numbers can be added to indicate the number of elements in a line or the accumulated total</font></span></div><div class="" style="margin-top: 0px; margin-bottom: 0px;"><span class="s1"><font class="" color="#7c2a00"><br class=""></font></span></div><div class="" style="margin-top: 0px; margin-bottom: 0px;"><font class="" color="#7c2a00">This change will make it easier for user to rearrange list, and eliminate the “Expected ‘,’ separator” error without making the code less safe or less readable. It also doesn’t have any impact on existing code since the user could still use the “,” manually</font></div><div class="" style="margin-top: 0px; margin-bottom: 0px;"><font class="" color="#7c2a00"><br class=""></font></div><div class="" style="margin-top: 0px; margin-bottom: 0px;"><span class=""><font color="#7c2a00" class="">There could be cases were the user will still need to type “,” if the grammar is ambiguous </font></span></div><div class="" style="margin-top: 0px; margin-bottom: 0px;"><span class=""><font color="#7c2a00" class=""><br class=""></font></span></div><div class="" style="margin-top: 0px; margin-bottom: 0px;"><span class="s1"><font class="" color="#7c2a00">The use of the ";" can also be eliminated using similar logic </font></span></div></div><div class="" style="margin-top: 0px; margin-bottom: 0px;"><span class="s1"><font face="Calibri" size="4" class=""><br class=""></font></span></div><img apple-inline="yes" id="E4F01174-139C-4A7E-8560-ACDC00D939DE" height="195" width="455" apple-width="yes" apple-height="yes" src="cid:5845C9B5-C4D1-45BA-832A-AE98B1E132B7" class=""><br class=""><div><blockquote type="cite" class=""><div class="">On May 10, 2016, at 2:05 PM, Karl Wagner via swift-evolution <<a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class=""><br class=""><blockquote type="cite" class="">On 10 May 2016, at 20:53, Chris Lattner via swift-evolution <<a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a>> wrote:<br class=""><br class="">Hello Swift community,<br class=""><br class="">The review of "SE-0084: Allow trailing commas in parameter lists and tuples" begins now and runs through May 16. The proposal is available here:<br class=""><br class=""><span class="Apple-tab-span" style="white-space:pre"> </span><a href="https://github.com/apple/swift-evolution/blob/master/proposals/0084-trailing-commas.md" class="">https://github.com/apple/swift-evolution/blob/master/proposals/0084-trailing-commas.md</a><br class=""><br class="">Reviews are an important part of the Swift evolution process. All reviews should be sent to the swift-evolution mailing list at<br class=""><br class=""><span class="Apple-tab-span" style="white-space:pre"> </span>https://lists.swift.org/mailman/listinfo/swift-evolution<br class=""><br class="">or, if you would like to keep your feedback private, directly to the review manager.<br class=""><br class="">What goes into a review?<br class=""><br class="">The goal of the review process is to improve the proposal under review through constructive criticism and contribute to the direction of Swift. When writing your review, here are some questions you might want to answer in your review:<br class=""><br class=""><span class="Apple-tab-span" style="white-space:pre"> </span>* What is your evaluation of the proposal?<br class=""><span class="Apple-tab-span" style="white-space:pre"> </span>* Is the problem being addressed significant enough to warrant a change to Swift?<br class=""><span class="Apple-tab-span" style="white-space:pre"> </span>* Does this proposal fit well with the feel and direction of Swift?<br class=""><span class="Apple-tab-span" style="white-space:pre"> </span>* If you have used other languages or libraries with a similar feature, how do you feel that this proposal compares to those?<br class=""><span class="Apple-tab-span" style="white-space:pre"> </span>* How much effort did you put into your review? A glance, a quick reading, or an in-depth study?<br class=""><br class="">More information about the Swift evolution process is available at<br class=""><br class=""><span class="Apple-tab-span" style="white-space:pre"> </span>https://github.com/apple/swift-evolution/blob/master/process.md<br class=""><br class="">Thank you,<br class=""><br class="">-Chris Lattner<br class="">Review Manager<br class=""><br class="">_______________________________________________<br class="">swift-evolution mailing list<br class="">swift-evolution@swift.org<br class="">https://lists.swift.org/mailman/listinfo/swift-evolution<br class=""></blockquote><br class="">I would love this, but I’d hate any language which allows it.<br class=""><br class="">Maybe we could degrade it to a warning instead of a compile error? So it’d be fine in scripts and when debugging, but you’ll be reminded that leaving it that way is not cool.<br class="">_______________________________________________<br class="">swift-evolution mailing list<br class=""><a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a><br class="">https://lists.swift.org/mailman/listinfo/swift-evolution<br class=""></div></div></blockquote></div><br class=""></body></html>