Fixed crash when deleting sections due to all objects being removed: #…

…116

Updated Swift API to match ObjC to support a nullable predicate on init of `RBQFetchRequest`.

Thanks to you @anlaital for these improvements!

Tweak to use the new ObjC interop functions in RealmSwift 2.1.1.

If you need earlier versions of RealmSwift use v5.0.0 or earlier.

Swift 3 support!

Fixed issue with Swift protocol not matching the ObjC protocol.

Made willPerformFetch/didPerformFetch optional on ObjC and Swift.

Fix for the the out of bounds crash while using RBQFRC without sectio…

…ns (specific to v4.0).

NOTE: IT IS NOT RECOMMENDED TO USE RBQFRC ANYMORE WITHOUT SECTIONS!

Realm recently introduced fine-grained notifications that work directly on a Realm collection. v4.0 of RBQFRC uses this API, and as such it adss no value unless you use RBQFRC with sections since Realm does not yet support grouping. This version fixes the crash so you can continue to use RBQFRC without sections, but it will make the UI updates slower and use more CPU than just using Realm's API directly.

Removed warnings from Swift. Requires Realm v0.99.1

Hot fix for v4.0 in which the index bounds in the cache for each sect…

…ion were not properly assigned.

Updated to support Realm v0.99 and fine-grain notification support.

Now RBQFetchedResultsController works with Realm directly! There is no more need to use RBQRealmNotificationManager or the customer notification methods.

Note: it is recommended to use Realm's fine-grain notification API directly, unless you need sections that RBQFetchedResultsController supports.

Finally, the issue around performing changes on different threads causing a deadlock is resolved!

Added a read only property to retrieve the section index titles.

Carthage support added!

Additional examples and repo restructuring.