<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=""><div><blockquote type="cite" class=""><div class="">On Feb 17, 2017, at 2:51 PM, Xiaodi Wu <<a href="mailto:xiaodi.wu@gmail.com" class="">xiaodi.wu@gmail.com</a>> wrote:</div><div class=""><div dir="ltr" class="">What a read! Two questions off the bat:<div class=""><br class=""></div><div class="">1. Any preliminary estimates as to what the performance cost of dynamic enforcement is shaping up to be, at least in an initial implementation? It'd have a direct impact on how "opt-in" the additional tools really are.</div></div></div></blockquote><div><br class=""></div>We don't have an initial implementation yet, sorry. I'm sure it'll vary a lot by the application. My hope is that it'll just be a few extra non-atomic loads and stores around every access, but it's possible that we'll need to make at least one of those an atomic exchange because it's legal for multiple threads to read concurrently. It hinges in part on how comfortable we are with allowing conflicts to escape dynamic detection in complex concurrent cases.</div><div> </div><div><blockquote type="cite" class=""><div dir="ltr" class=""><div class="">2. Without the intention of initiating premature bikeshedding, what was the thought behind proposing `inout foo = ...` vs the seemingly more obvious `var foo: inout = ...`, given that `inout` was moved to the type side of the colon?</div></div></blockquote><div><br class=""></div>Well, I think it's pretty semantically different from a var. It's also really tempting to read the latter as "a var of inout type", suggesting that a re-assignment would bind it to different storage, which is not how it works, should work, or even could work.</div><div><br class=""></div><div>John.</div><div><br class=""><blockquote type="cite" class=""><div dir="ltr" class=""><div class=""><br class=""><div class="gmail_extra"><br class=""><div class="gmail_quote">On Fri, Feb 17, 2017 at 11:11 AM, John McCall via swift-evolution <span dir="ltr" class=""><<a href="mailto:swift-evolution@swift.org" target="_blank" class="">swift-evolution@swift.org</a>></span> wrote:<br class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word" class=""><div class=""><span class=""><blockquote type="cite" class=""><div class="">On Feb 17, 2017, at 12:08 PM, John McCall <<a href="mailto:rjmccall@apple.com" target="_blank" class="">rjmccall@apple.com</a>> wrote:</div><div class=""><div style="font-family:Helvetica,Arial;font-size:13px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(254,254,254)" class=""><blockquote type="cite" style="margin:15px 0px" class=""><div style="margin-top:0px" class="">On Feb 17, 2017, at 4:50 AM, Adrian Zubarev <<a href="mailto:adrian.zubarev@devandartist.com" style="color:rgb(65,131,196);background-color:inherit;text-decoration:none" target="_blank" class="">adrian.zubarev@devandartist.<wbr class="">com</a>> wrote:</div><div style="margin-bottom:0px" class=""><div style="word-wrap:break-word" class=""><div class="m_-3673187207325266430bloop_markdown"><p style="margin:15px 0px" class="">Hi John, would you mind creating a markdown document for this manifesto in<span class="m_-3673187207325266430Apple-converted-space"> </span><a href="https://github.com/apple/swift/tree/master/docs" style="color:rgb(65,131,196);background-color:inherit;text-decoration:none" target="_blank" class="">https://github.com/apple/<wbr class="">swift/tree/master/docs</a>? :)</p><div class=""><br class=""></div></div></div></div></blockquote>Yes, it should go in the repository. That commit is pending, but the in meantime, you can see the document properly rendered at:</div><div style="font-family:Helvetica,Arial;font-size:13px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(254,254,254)" class=""> <font color="#4183c4" class=""><a href="https://github.com/rjmccall/swift/blob/4c67c1d45b6f9649cc39bbb296d63663c1ef841f/docs/OwnershipManifesto.md" target="_blank" class="">https://github.com/rjmccall/<wbr class="">swift/blob/<wbr class="">4c67c1d45b6f9649cc39bbb296d636<wbr class="">63c1ef841f/docs/<wbr class="">OwnershipManifesto.md</a></font></div></div></blockquote><div class=""><br class=""></div></span>Ah, and of course the second I send this, my PR gets merged. :)</div><div class=""><br class=""></div><div class="">The new URL is:</div><div class=""> <a href="https://github.com/apple/swift/blob/master/docs/OwnershipManifesto.md" target="_blank" class="">https://github.com/apple/<wbr class="">swift/blob/master/docs/<wbr class="">OwnershipManifesto.md</a></div><span class="HOEnZb"><font color="#888888" class=""><div class=""><br class=""></div><div class="">John.</div></font></span></div><br class="">______________________________<wbr class="">_________________<br class="">
swift-evolution mailing list<br class="">
<a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a><br class="">
<a href="https://lists.swift.org/mailman/listinfo/swift-evolution" rel="noreferrer" target="_blank" class="">https://lists.swift.org/<wbr class="">mailman/listinfo/swift-<wbr class="">evolution</a><br class="">
<br class=""></blockquote></div><br class=""></div></div></div>
</blockquote></div><br class=""></body></html>