Open Wonko7 opened 5 years ago
CLJS has been quite a moving target, so it's not surprising when warnings appear that didn't appear before. I'm not familiar with shadow-cljs so I don't know if that can have different warnings than other cljs compilation methods. If you or anyone figures this out, I'm happy to accept a pull request for it.
Hi @Wonko7, I'm currently compiling my project with shadow-cljs, using 1.1.3-SNAPSHOT and not seeing that warning compiling similar code. Are you still getting the warning? If so, what version of shadow-cljs are you using?
I agree with @pseudonamed ...something in 1.1.3-SNAPSHOT fixes the warning.
That's weird, I'm using [com.rpl/specter "1.1.3-SNAPSHOT"]
with shadow-cljs 2.8.52, and I'm still getting :redef-in-file
warnings on setval with the message pathcache77013 at line 123 is being replaced
.
What could I be missing?
@Wonko7, I'm unsure; can you create a minimal public repo that reproduces the error?
Yes, it's an interaction between cloroutine & specter: https://github.com/Wonko7/warning-specter-async
Hi!
I'm requiring it like this:
Am I doing something wrong?
I'm using:
[com.rpl/specter "1.1.3-SNAPSHOT"]