JP Simard

@asjesset what would you like to see improved in Realm to make your use case easier? Would it make sense to have "new" variants of `deletions`, `insertions`, `modifications` on `RLMCollectionChange`?...

@Kirow since your comments are unrelated to this ticket (tracking adding new functionality to changeset notifications), I've created a new issue where we can discuss the problems you're facing: #4016....

A few thoughts on this: ``` swift class Foo: Object {} ``` Here `Foo` isn't just _one_ type, it's an "archetype": think of it like an abstract type that can't...

I certainly understand that, but it doesn't change anything in my last response. Here's something we _could_ technically do, but it'd be a ton of work and IMO likely not...

No we have not implemented this.

Agreed, this is something we want to do, which is why we're tracking it here.

This is great @SimplyDanny! I've turned this on for Lyft's codebase and the consensus is that folks like it. I ran into 3 kinds of minor issues with the rule's...

> Correct handling of trivia is a really unpleasant task. I agree. SwiftSyntax doesn't make it easy. I keep hoping I'm going to have a "lightbulb" moment at some point...

> It would probably make sense to have our own "trivia library" in SwiftLint. I wonder if this would make sense in the SwiftSyntax repo itself. To start we could...

I'm happy to merge this now but the PR is marked as draft. Did you still want to work on this before I merge?