Use of dispatch_get_current_queue about flox-objc HOT 5 CLOSED

Thanks for the heads-up — I actually did not notice the deprecation because I'm always using iOS 5 as deployment target, and it doesn't show up in that case. ;-)

Bah, it's a bummer that they're taking that method away. The idea was that it would always return in the same thread queue as the one it was being called from. Which will very probably be the main queue, you're right — but if not, it's a problem. I'll have to investigate this! Didn't find a nice solution from the first few minutes of googling. ;-)

from flox-objc.

I decided to use dispatch_get_main_queue instead. I liked the old solution better, but let's just say that Apple will probably maybe have had a good reason to remove get_current_queue.

from flox-objc.

Ok cool, so typically this might have been main_queue anyway? i wasn't sure if there were any internal uses of queues besides the io queue that could cause any deadlock issue if the main_queue was used explicitly.

from flox-objc.

Yes, this should always have been "main_queue", except if users called some Flox commands from different queues, which is unlikely. So I guess the change shouldn't be a problem.

from flox-objc.

That said: if turns out to cause any problems, we could always add an option to specify the queue people want their callbacks to be executed.

from flox-objc.