having the same issue as @kommen

Don’t know, seems like a result of a combination of multiple different forms.

seems odd that it doesn't complain about the and uses above

as said above, for me the warning pops up only when the file is changed as well, initial compilation doesn’t trigger anything

also prod build with figwheel-main went without errors

yeah but in the snippet you posted and is used 3 times and only warns on the last one. that is weird since its all compiled in the same pass.

In that 3rd and I’ve wrapped one of the subexpressions with (not ...) and the error is gone now

Smells like it could be related to truthy-induced, as that and involves simple symbols and it may expand to a case that triggers something based on that. (I can't see how.) But if you can repro it by switching back to involving simple symbols, then seeing if https://github.com/bhauman/figwheel-core/pull/2 fixes it would be valuable.

2 fixed it for me

Cool. That's good news.

@mfikes tried it, the error is gone 🎉

Cool!

@mfikes I think worth waiting a bit just to see what falls out of the latest

still hearing reports of small things here and there

With respect to version numbers? Yeah, I'm mostly just curious about the process of when the bump to 11 occurs.

in the past we did bump after Clojure was released

and we're more or less going to do that - but no rush