There are some signs that there are some regressions in CLJS with regards to exceptions and spec? https://github.com/jeaye/orchestra/issues/41#issuecomment-461649942

there also seems to be a regression resulting in Can't take value of macro . warnings https://clojurians.slack.com/archives/CALJ3BFLP/p1549456266299400

we’re also seeing this warning sometimes for cljs.core/exists?, but I couldn’t repro it yet in a minimal example

https://cloudflare-ipfs.com/ipfs/QmayUT2UccKDKgppzdFpk1t7PmrPPTymy8weyL9uGvbYfL

JIRA?

That's the second time that I see this kind of when+and report on newer cljs. I think that is some optimization problem with type inference

@borkdude none yet, wasn’t sure if this is an actual cljs issue or if its tooling related

can you say how to reproduce it? which steps to take? I can do a quick check if it happens in shadow-cljs as well?

@thheller can’t reproduce it yet with specific set of steps. will report back when I can do so

The only hunch I have with respect to spurious analysis errors and Figwheel is https://github.com/bhauman/figwheel-core/pull/2

It was a heisen-situation for me. I believe it was after saving a macro file, but manually doing a browser refresh cleared it. I'll try to keep an eye out for a repro as well.

Okay I hit it.