<div dir="ltr">Whew! Thanks for the heads-up before my prototype hits merge-conflict madness. :)<div><br></div></div><br><div class="gmail_quote"><div dir="ltr">On Tue, Aug 22, 2017 at 1:16 PM Ben Rimmington <<a href="mailto:me@benrimmington.com">me@benrimmington.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">> On 22 Aug 2017, at 17:08, Tony Allevato wrote:<br>
><br>
> A few months ago (before Swift 5 chatter started), I pitched an idea to improve the use of @availability in third-party code by eliminating deprecation warnings in same-file references. We had some good discussion there about who needed same-file deprecation vs. same-module deprecation and so forth, and I was convinced that a better approach would be to allow @available to be enforced based on accessibility.<br>
<br>
FYI<br>
<br>
Excise "Accessibility" from the compiler:<br>
<<a href="https://github.com/apple/swift/pull/11504" rel="noreferrer" target="_blank">https://github.com/apple/swift/pull/11504</a>><br>
<br>
> @jrose-apple (Jordan Rose) wrote:<br>
><br>
> "Accessibility" has a different meaning for app developers, so we've already deliberately excised it from our diagnostics in favor of terms like "access control" and "access level". Do the same in the compiler now that we aren't constantly pulling things into the release branch.<br>
><br>
> (This isn't exactly important, but we might as well clean it up.)<br>
</blockquote></div>