On Fri, Oct 4, 2013, at 10:16 AM, Jens Alfke wrote: > Basically, by calling a client-supplied block on its private internal > queue, the implementation is exposing sensitive internal state to its > callers. That seems like a really bad idea.
This jibes with my memory of Andy's argument, which I'm afraid is lost to the annals of Twitter history. However, there's a very cogent thread on GitHub about a the relative (un)safety of letting queues escape your control, in the context of dispatch_get_current_queue() and queue targeting: //github.com/jspahrsummers/SafeDispatch/issues/1 --Kyle Sluder _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
