Realm-java: Breaking WishList for 5.0

[cmelchior]

This ticket is for general discussion of the breaking changes in a future 5.0 release. Some items have been moved from #4785

Please edit the main post to add a topic with a sequence number, and we can discuss it in the comments. If the breaking change is decided to be worthy to add, then create a separate issue for it.

1. Do not allow having both typed Realm instance and Dynamic Realm instance on the same thread. Throw an exception instead. This creates lots of troubles with Realm instance cache management. By disallowing it, the RealmCache implementation can be much simpler and give us an option to totally manage the Realm instance through Object Store.

2. Remove the mips so file since there is NO mips device in the market. Perhaps consider having a parameter in the realm closure for including mips/arm but not have them be part of the standard library. We would need to modify our build system for that.

[Zhuinden]

Change the behavior of distinct() to work against query result. See #4774

Isn't this the same as

Calling distinct() on a sorted RealmResults no longer clears the sorting (#3503).

?

I'm sure that was fixed in https://github.com/realm/realm-java/pull/3522#issuecomment-328304653

[cmelchior]

Yup. I closed the issue. Thanks 👍

[Zhuinden]

My most severe breaking change wish would be to rename

Realm.getInstance(RealmConfiguration) to Realm.open(RealmConfiguration)

Realm.getDefaultInstance() to Realm.open()

Realm.getInstanceAsync(RealmConfiguration) to Realm.openAsync(RealmConfiguration)

Realm.getDefaultInstanceAsync() (which does not exist) to Realm.openAsync()

[Zhuinden]

I feel like the new sort mechanics should have the keyword sorted instead of just sort.

[cmelchior]

Replaced by #6500