Given the number of objects Core Data is designed to juggle, managing that number of weak references might well affect performance. Besides, wouldn’t you still the same result, that your object has a nil reference to the context because the context has been deallocated?
Furthermore, I think you can also observe this affect on deleted objects once the context has been saved, if you’re still holding a reference to any such objects. Mike. Sent from my iPhone > On 26 Mar 2019, at 21:57, Rick Mann <rm...@latencyzero.com> wrote: > > The implication there is that an object has a weak reference to the MOC? Ah, > in the header I see it's `assign`. I wonder why they do that and not `weak`. > > Thanks, I'll look into it. > >> On Mar 26, 2019, at 14:50 , Richard Charles <rcharles...@gmail.com> wrote: >> >> You have retained the managed object outside the managed object context. >> >> --Richard Charles >> >> >>> On Mar 26, 2019, at 1:04 PM, Rick Mann <rm...@latencyzero.com> wrote: >>> >>> I'm seeing a situation where my NSManagedObject's managedObjectContext is >>> nil. It doesn't happen all the time though. Any idea why? Thanks! >>> >>> -- >>> Rick Mann >>> rm...@latencyzero.com >> > > > -- > Rick Mann > rm...@latencyzero.com > > > _______________________________________________ > > Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) > > 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/mabdullah%40karelia.com > > This email sent to mabdul...@karelia.com _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) 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 arch...@mail-archive.com
