<div dir="ltr">Adrian and Karl,<div><br></div><div>OK, thanks for the constructive feedback.</div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Nov 30, 2016 at 11:45 AM, Karl <span dir="ltr"><<a href="mailto:razielim@gmail.com" target="_blank">razielim@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class=""><br>
> On 30 Nov 2016, at 14:11, Steve Prescott via swift-evolution <<a href="mailto:swift-evolution@swift.org">swift-evolution@swift.org</a>> wrote:<br>
><br>
> As the original poster of this thread, I wanted to re-state the original question:<br>
><br>
> Should enums REQUIRE parameter names?<br>
><br>
> Pro: The syntax would more closely match that for functions, which requires names for all parameters (unless you say “_”) vs. the current syntax that is sort of C-like.<br>
> Con: More verbose<br>
><br>
> With this suggestion, your declaration of a variable that uses an enum would resemble calling a function. e.g.:<br>
><br>
> var myTeam = Team.football (name: “Redskins”, city: “Washington, DC”, quarterback: “Kirk Cousins”)<br>
><br>
<br>
</span>I don’t think they should be required. The payload is actually a tuple, and element names are not required for tuples (and not even supported for single-element tuples).<br>
<br>
Your example is still possible without requiring labels; all that would change is that code which works today would suddenly break. Unless I’m mistaken, your proposal is about removing functionality and does not add anything.<br>
<span class="HOEnZb"><font color="#888888"><br>
- Karl</font></span></blockquote></div><br></div>