Phillip Mates

Any updates on this @cursive-ide ? I think I'm going to close it here given that there is nothing `matcher-combinators` can do to address this; at least as far as...

@sovelten and I explored something along these lines in the past. Not to say it shouldn't be looked into again, but wanted to share our observations: 

some examples of how to do this in user land: ```clojure (defn roughly-same-time [expected] (matcher-combinators.core/->PredMatcher (fn [actual] (and (instance? java.time.Instant actual) (.isAfter expected (.plus actual -5 java.time.temporal.ChronoUnit/SECONDS)) (.isBefore expected (.plus...

Hmm, I thought I merged @plexus's fix for the `:matcher-combinators/mismatch` issue (https://github.com/nubank/matcher-combinators/pull/49). Though looking at it I may have forgotten to update the cljs code :( My cljs dev env...

https://github.com/nubank/matcher-combinators/pull/189 has been released in `3.8.2` and I think should address this. If not, let me know and I can look into it further

hey @alexander-yakushev, I kinda forgot about the context around this issue / am no longer using compliment/in need of the change. If it looks like something useful in general feel...

I also like it; definitely gives some context to the magic that happens via `clojure.test/assert-expr`. :+1: for a PR with these changes

Hi, yes this seems to be a bug in the implementation. `absent` is implemented in a sort of tricky way but I think we can try tracking when an `any-of`...

hey, thanks for raising this Matching sets or `in-any-order` has very bad performance due to the fact that the library tries every permutation in an attempt to find the smallest...

Thanks for the comprehensive testing @lread for ```clojure (is (match? [1 82 3 4 2 7 9 10] [1 2 10 11]) "recover multiple mismatches") ``` the current behavior gives...