<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div><br><br>Sent from my iPad</div><div><br>On May 10, 2016, at 12:53 AM, Andrew Trick <<a href="mailto:atrick@apple.com">atrick@apple.com</a>> wrote:<br><br></div><blockquote type="cite"><div><meta http-equiv="Content-Type" content="text/html charset=utf-8"><br class=""><div><blockquote type="cite" class=""><div class="">On May 9, 2016, at 4:07 PM, Matthew Johnson <<a href="mailto:matthew@anandabits.com" class="">matthew@anandabits.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><span style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;" class="">I’m also interested in your feedback on whether a proposal around indirect is something worth pursuing right now or whether that is something that should wait until after Swift 3.</span></div></blockquote></div><br class=""><div class="">I’m not prepared to champion this for Swift 3, I think there are enough other important proposals on the table, and this is an area that requires careful design. </div></div></blockquote><div><br></div><div>That's what I suspected and why I asked before taking time to write something up. I'll be patient and look forward to this in the future.</div><div><br></div><div>I should add that if a decisions on the changes Dave is looking for must happen in Swift 3 or never I support doing it. While I am concerned about the boilerplate I would prefer some boilerplate in the short term to a suboptimal design in the long term.</div><br><blockquote type="cite"><div><div class="">If I did have to pick features that we touched on in this thread from most to least important I would say:</div><div class="">1. Indirect structs</div><div class="">2. Mutability of reference/class types</div><div class="">3. Automation or annotations for CoW types.</div><div class="">4. Annotations that constrain function side effects.</div></div></blockquote><div><br></div><div>That sounds like the right priorities to me as well. </div><br><blockquote type="cite"><div><div class=""><br class=""></div><div class="">-Andy</div></div></blockquote></body></html>