Daniel Bechler

Ha, that sounds reasonable! :smile: The good news about diffing is, that I started working on a `Differ` for ordered collections, which involves an algorithm that can probably also be...

@Wolfgang-Winter Looks good to me! I'll keep both strategies in mind, when I start working on this.

Yes, this is intentional. Different types are currently only allowed for Maps and Collections. Treating different types properly is pretty tricky so I didn't want to focus on it until...

I fully agree with all you're saying. This is really valuable feedback. Thank you for that. I'm glad you found a workaround and I will definitely put it on the...

This issue has been tackled in release [0.12](https://github.com/SQiShER/java-object-diff/releases/tag/java-object-diff-0.12). The solution could work for your scenario, but I'm not entirely sure. I'm closing this issue for now, but feel free to...

Hi @jlsalmon, yes, I think what you expect is reasonable and should be the result of the example you've given. It's the path of least surprise and makes total sense....

@jlsalmon Not yet. You?

@jlsalmon Cool, thanks for looking into it! I think both solutions would be fine. The first one is probably a little cleaner, because the `BeanDiffer` is technically the generic `Differ`...

Currently all `Collections` are treated like `Sets`: - It is assumed there can be only one instance with the same identity (via `hashCode` & `equals`) - Order is completely disregarded...

Good job! Especially the ordered strategy raises some interesting questions. Your current implementation reports positional changes as `REMOVE` or `ADD`. However, I think for a more generic approach it would...