Fixes CoreData Threading Warnings #322
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Due to Xcode 6 CoreData threading violations, each userInfo call should be wrapped up by a performBlock call. This should be executed by every single NSManagedObject that gets faulted / inserted into any context, and has a considerable performance impact. Let’s bring back the old school obc_setAssociatedObject, which was the default mechanism in Simperium Mk 0.5.0
jleandroperez
added a commit
that referenced
this pull request
Jul 28, 2014
Fixes CoreData Threading Warnings
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #305
NSManagedObjectContext.userInfousage should be wrapped up byperformBlock:calls, with a considerable performance impact. Let's bring back the old school object-association mechanism.