On Oct 3, 2013, at 11:46 AM, Kyle Sluder <[email protected]> wrote: > There is magic sauce in CFRunLoop that runs the main queue as part of > processing the runloop. All other queues are managed by code running on > a thread managed by libdispatch. The main queue is a special case; it > doesn't make sense for this relationship to exist for other queues.
Why doesn’t it make sense? A runloop is conceptually very much like a serial dispatch queue. Both are mechanisms for handling incoming requests/calls/events in order. Why are the two divorced, except for the special case of the main thread? I think this would fix some current problems. For example, dispatch_get_current_queue is deprecated, and the only reason I can think of is that it may return NULL if the caller isn’t running under the control of a dispatch queue. If threads with runloops had dispatch queues, then dispatch_get_current_queue would work correctly in this very common case, making it more reliable. —Jens _______________________________________________ Cocoa-dev mailing list ([email protected]) 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 [email protected]
