I’m still not a fan of the API idiom of accepting a queue on which to run callbacks. There are dangers there… but maybe they’re academic.
Conversation
. Worried about composition wrt target queues, APIs which mutate queues, and resilience against future concurrent APIs.
2
1
Show replies
Replying to
: it’s a trust issue. If you want a specific queue, it’s easy to put yourself on it.
Replying to
: I’m also a big proponent of only allowing execution to cross module boundaries on the main thread. Because expectations.
1
I’m also okay with allowing boundary crossing on “an arbitrary global concurrent queue” because you’ll have to do the same things.
1
Show replies
Execute callbacks on “an arbitrary global concurrent queue.”
1
Show replies
Replying to
so which queue should it run the callback on? Unspecified? Main? I personally prefer main if called from main, unsp. if not.
1
Unspecified. I can be swayed if the API specifically regards UI in some way.
1
1
Show replies