<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Dec 21, 2015, at 12:25 PM, Joe Groff via swift-evolution &lt;<a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a>&gt; wrote:</div><br class="Apple-interchange-newline"><div class=""><meta http-equiv="Content-Type" content="text/html charset=us-ascii" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div class=""><blockquote type="cite" class=""><div class="">On Dec 19, 2015, at 4:10 PM, Erica Sadun &lt;<a href="mailto:erica@ericasadun.com" class="">erica@ericasadun.com</a>&gt; wrote:</div><br class="Apple-interchange-newline"><div class=""><meta http-equiv="Content-Type" content="text/html charset=utf-8" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class="">What would the ramifications of the following be? Each addresses the "confusable with labeling" issue but preserve the inout keyword.</div><div class=""><br class=""></div><div class=""><font face="Courier" class="">func foo(x: inout Int)</font></div><div class=""><span style="font-family: Courier;" class="">func foo(x: @inout(Int))</span></div><div class=""><font face="Courier" class="">func foo(x: @inout Int)</font></div><div class=""><br class=""></div><div class="">Is there an underlying reason that parameter modification should live on the name side rather than the type side of the colon? They aren't really modifying the name</div><div class=""><br class=""></div><div class="">-- Erica, inexperienced with Rust</div></div></div></blockquote><br class=""></div><div class="">Putting `inout` after the colon feels good to me. Like Jordan said, it meshes better with the type syntax, (inout Int) -&gt; (), too.</div><div class=""><br class=""></div></div></div></blockquote><div><br class=""></div><div>+1. &nbsp;I like it.</div><br class=""><blockquote type="cite" class=""><div class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class="">-Joe</div><br class="">
<img src="https://u2002410.ct.sendgrid.net/wf/open?upn=eLFMrKDT8iBxZ-2Fbnk-2BZqvSchNN-2FvYXdceA0T7VxwkAekakz-2BwPN-2FG-2F8lLRVN6iN0ZPtmlhDSr6li5rICfBiNGck9K7Pg4Efn6D2Gw1l2vskZzvSKSgXCg3aueg8zBNfxOULY2Qw-2BkLdbbcnSExqgve7ZkyY4obczXYBs3XAVNniHMlLLmW8v0mCGsF3NzNv8eZMHDvX1P-2F5YjANW07irNJyfb-2F-2FgkFqNutaOWK-2BMe1w-3D" alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;" class="">
</div>
_______________________________________________<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></blockquote></div><br class=""></body></html>