`- (id)objectInRealm:atIndexPath:` is needed?

[roobiq]

`- (id)objectInRealm:atIndexPath:` is needed?

[bigfish24]

That method was put in place along side:

initWithFetchRequest:sectionNameKeyPath:inMemoryRealmCache:

so that you could create the in-memory Realm external to the FRC. I really should rethink this, because if anything you should only be passing in the identifier to the in-memory Realm, since presumably you already have a strong reference to it elsewhere.

Secondly, I added support for in-memory Realm cache by simply passing nil for the cache name in the other init method.

I think how in-memory caching in the FRC is handled needs to be simplified, with both of these methods deprecated. I can't think of a use case in having the Realm used for the cache be created outside of the FRC. The only reason I did this initially was for the RBQFetchedResultsControllerDelegateTests.

[bigfish24]

If I remember correctly in-memory Realms initially were not accessible across threads, which in some way led to this early thinking in the API.

[bigfish24]

Fixed in this PR: #23