strange behaviour I ran into:
(let [foo {:a {:b 1}}]
(m/match (:a foo)
{:b ?x} ?x))
;; => Error: non-exhaustive pattern match
splicing the value of (:a foo) into the value position works as expected
@qythium I see the problem. I’ll get a patch for that ASAP.
Yeah that one is probably my fault.
I will be that instead of seeing that keyword as a function call it thinks it is a seq and based in type inference fails.
Definitely a bug. I can fix after my lunch break if noprompt doesn't. Nice the (:a foo) to a let binding and I bet it works. Sorry about that.
@jimmy I’m good to let you handle it if you’d like. 🙂 You might be able to fix that one faster than me. 🙂
Either way, we’ll fix it as quickly as possible @qythium
[meander/epsilon "0.0.377"]
• Fixes overzealous seq type inference