(match #{false} #{false}) fails

[dchelimsky]

(core/match #{false} #{false})
;; => {:matcher-combinators.result/type :mismatch,
;;     :matcher-combinators.result/value #{false {:actual false}},
;;     :matcher-combinators.result/weight 1}

Also, because in-any-order uses the same underlying mechanism as set matchers:

(core/match (m/in-any-order [false]) [false])
;; => {:matcher-combinators.result/type :mismatch,
;;     :matcher-combinators.result/value (false {:actual false}),
;;     :matcher-combinators.result/weight 1}

[dchelimsky]

FYI - I discovered this adding a property test for the equals matcher:

(defspec equals-matchers
  {:num-tests 100
   :max-size  10}
  (prop/for-all [v gen/any-equatable]
                (core/match?
                 (core/match (matchers/equals v) v))))

;; produces

{:shrunk
 {:total-nodes-visited 11,
  :depth 1,
  :pass? false,
  :result false,
  :result-data nil,
  :time-shrinking-ms 1,
  :smallest [#{false}]},
 :failed-after-ms 13,
 :num-tests 36,
 :seed 1590595380500,
 :fail [#{false \:}],
 :result false,
 :result-data nil,
 :failing-size 5,
 :pass? false,
 :test-var "equals-matchers"}

[philomates]

ha, this is an awesome bug! I'm having fun imagining what the buggy code looks like :)
yay generative tests, was actually wondering how you came across this

[philomates]

addressed in #133