<div dir="ltr">On Tue, Dec 8, 2015 at 12:45 PM, Brent Royal-Gordon <span dir="ltr"><<a href="mailto:brent@architechies.com" target="_blank">brent@architechies.com</a>></span> wrote:<br><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">> It may not be possible or economical for those projects to get updated versions of those frameworks with nullability attributes.<br>
<br>
</span>Objective-C nullability attributes don’t affect their binary compatibility, though, right? As long as Swift’s bridging behavior is *safe*, anyone can fix them being *inconvenient* by editing the headers in the crappy old frameworks they’re using.<span class="HOEnZb"><font color="#888888"><br>
</font></span></blockquote></div><br></div><div class="gmail_extra">In an ideal world, absolutely. In the business world, that's contingent on what contracts have been signed. Some commercial frameworks require that customers not edit any part of the framework, including headers.</div></div>