<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=""><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. 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 class=""><br class=""></div><div class="">-Andy</div></body></html>