Bryan Jones

Nothing on this proposal? Realm *does* list macOS as an official platform, but this API is essentially UIKit-only. It would be nice if Realm were a proper fit on all...

The problem is more extensive than just `modifications && (insertions || deletions)`. The problem can manifest anytime there are BOTH `insertions` and `deletions` in a changeset. This happens, for example,...

@nirinchev wouldn't it be non-breaking to simply add an option to the collection change subscription that controls how the indexes are calculated? The default would be the current behavior (indexes...

I realize the object naming is more cumbersome than `foo` and `bar`, but I wanted to match the screenshot of my actual code. `MasterCue` Objects model sound clips. They have...

@tgoyne Thanks! That would be a very good clarification to make in the `Map` docs because there is a reasonable presumption that the collection might behave the way other Realm...

@tgoyne When using Atlas Device Sync, if I simply delete the object that is the value (instead of first removing it from the Map), on MongoDB's website the Map (the...

@tgoyne On the MongoDB Forums, Jay informed me of yet more incongruent behavior here: 1) If I explicitly set a Map value to nil, both the value and its key...

 Above, `cueNotes` is a `Map`. You can see that my local copy of it in Swift has 3 keys with null placeholder values that...

@nirinchev if the keys are important, why are they deleted if I explicitly set a Map value to nil? (`myMap["someKey"] = nil`) It's just very inconsistent behavior and it's not...

@nirinchev All of that seems reasonable. It resolves all the inconsistencies, at least. When you update the docs, I would stress that `Map` isn't really the correct collection to use...