<div dir="ltr"><div>>Swift 2.2 code should be run through a migrator, which is able to automatically handle changes like this.</div><div><br></div>Yes, but that's not really my point. Why do it this "magical" way? It's already possible (and actually very easy) to wrap C modules such as libdispatch in a Swifty API (see <a href="https://github.com/VeniceX/Venice">Venice</a>, <a href="https://github.com/Zewo/OpenSSL">OpenSSL</a>, <a href="https://github.com/Zewo/PostgreSQL">PostreSQL</a> as examples). I know that LibDispatch is special to Swift and Apple, but I just don't see a reason to give it such a special treatment.<div><br></div><div>Dan</div></div><br><div class="gmail_quote"><div dir="ltr">On Thu, May 19, 2016 at 9:56 PM Chris Lattner <<a href="mailto:clattner@apple.com">clattner@apple.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
> On May 19, 2016, at 9:53 PM, Dan Appel <<a href="mailto:dan.appel00@gmail.com" target="_blank">dan.appel00@gmail.com</a>> wrote:<br>
><br>
> Does this mean that all current code using Dispatch is broken?<br>
<br>
Are you asking about Swift 2.2 code?<br>
<br>
Swift 2.2 code is generally completely incompatible with Swift 3 for a lot of other reasons (e.g. major changes to the standard library APIs). Swift 2.2 code should be run through a migrator, which is able to automatically handle changes like this.<br>
<br>
-Chris</blockquote></div><div dir="ltr">-- <br></div><div><div dir="ltr"><div><div>Dan Appel<br></div></div></div></div>