<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="">I just re-read your initial objection, which had a slightly different idea: allow inlining, but if the library has changed when I go to run it, refuse to launch. I wanted to respond to that explicitly: this is no different from treating the library as part of your own distribution (what the document calls a "resilience domain"), and then <i class="">not shipping it</i> with your app. That means I see two options:<div class=""><br class=""></div><div class="">- Mark a dependency as version-locked; if the library changes in any way, refuse to launch.</div><div class="">- Mark a dependency as non-inlineable.</div><div class=""><br class=""></div><div class="">I think these are both client-side controls, perhaps things you put in your Manifest.swift file. I'm <i class="">not</i> sure that we actually need or want both of them, but does this formulation seem reasonable to you?</div><div class=""><br class=""></div><div class="">Jordan</div><div class=""><br class=""></div><div class="">P.S. I hope I'm not coming off as antagonistic in these emails, particularly with the repeated responses. I think you've brought up a very important issue and it's critical that the ramifications of the model, whatever we decide on, are well-understood and can be meaningfully acted upon.</div></body></html>