Originally created by @SteveKChiu on GitHub (Jul 9, 2015).
I am not sure why this assert is needed, as the code show it immediately jump to different queue.
This is what I am doing, I fetch json from server in different queue; upon completion I call .beginAsynchronous to start transaction to store the object, and at that time the queue is NOT main queue.
So my question is whether it is absolutely necessary to call .beginAsynchronous in the main thread? Or we can remove this assertion?
Originally created by @SteveKChiu on GitHub (Jul 9, 2015).
I am not sure why this assert is needed, as the code show it immediately jump to different queue.
This is what I am doing, I fetch json from server in different queue; upon completion I call .beginAsynchronous to start transaction to store the object, and at that time the queue is _NOT_ main queue.
So my question is whether it is absolutely necessary to call .beginAsynchronous in the main thread? Or we can remove this assertion?
@SteveKChiu You're right, they are completely unnecessary and should be thread-safe without them. There's probably a couple more places where thread checks are overprotective, but I'll remove the ones from the beginXXXX() methods. Thanks!
@JohnEstropia commented on GitHub (Jul 9, 2015):
@SteveKChiu You're right, they are completely unnecessary and should be thread-safe without them. There's probably a couple more places where thread checks are overprotective, but I'll remove the ones from the `beginXXXX()` methods. Thanks!
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @SteveKChiu on GitHub (Jul 9, 2015).
I am not sure why this assert is needed, as the code show it immediately jump to different queue.
This is what I am doing, I fetch json from server in different queue; upon completion I call .beginAsynchronous to start transaction to store the object, and at that time the queue is NOT main queue.
So my question is whether it is absolutely necessary to call .beginAsynchronous in the main thread? Or we can remove this assertion?
@JohnEstropia commented on GitHub (Jul 9, 2015):
@SteveKChiu You're right, they are completely unnecessary and should be thread-safe without them. There's probably a couple more places where thread checks are overprotective, but I'll remove the ones from the
beginXXXX()methods. Thanks!