<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="">I don’t believe any more so than for let or var, which this effectively is a complement for.<div class=""><br class=""></div><blockquote style="margin: 0 0 0 40px; border: none; padding: 0px;" class=""><div class="">func foo(var externalName internalName:String) { print(internalName) }</div></blockquote><div class=""><br class=""></div><div class="">-DW</div><div class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Dec 5, 2015, at 7:25 PM, Tal Atlas <<a href="mailto:me@tal.by" class="">me@tal.by</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class="">This syntax is confusing with that of defining the external keyword for the parameter.</div><br class=""><div class="gmail_quote"><div dir="ltr" class="">On Sat, Dec 5, 2015 at 9:24 PM David Waite via swift-evolution <<a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a>> wrote:<br class=""></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">A possible syntax, then:<br class="">
<br class="">
init(set name:String, set score:Int) { }<br class="">
<br class="">
set would be a fourth parameter modifier alongside let, var, and inout - only valid on initializers (not as useful and likely confusing in other contexts). The local name has to match a parameter on the type. Like let/var (but unlike inout) usage of ‘set’ on a initializer parameter does not affect the caller or prototype conformance.<br class="">
<br class="">
-DW<br class=""></blockquote></div></div></blockquote></div><br class=""></div></body></html>