A Brooks

This is an interesting idea, and I agree that it would make the output easier to interpret. I haven't noticed deep-diff output being out of order, possibly because I mostly...

I think there are two ideas here: * Add support for `flatland.ordered` collections. This should be done in a bring-your-own-dependency fashion—we don't want to pull in this library if people...

I think there are two issues, and I think they're really two manifestations with the same issue. `(not= ##NaN ##NaN)` which breaks `diff`, but it also breaks our tests. `matchers-combinators`...

Glad I put my research into writing, but I don't think this should be a priority for the moment.

I think this makes sense to leave something open as a documentation fix. Fixing the underlying problem probably won't be a priority, so this can be closed as "PR welcome"...

@justindbelanger Thanks! This LGTM, but do you want to make the docstring changes in the same PR? The only reason I can think of to not do it is if...

@justindbelanger If you ever want to come back and update the docstrings, that'd be great, but in the meantime, I thought I'd merge this. Thanks! ![A tiny cartoon mouse spinning...

I can look into Leiningen's support for this feature.

What do you think of Tobias' solution? >Given a project foo/bar that has versions 1.0.0 and 2.0.0, and there is a desire to move to com.foo/bar, the project owner could:...

I experimented with something similar: https://github.com/lambdaisland/deep-diff2/pull/46. The way the screenshot is displaying it is probably not very readable, however. I think implementing a condition for `print-mismatch` like you suggest could...