Open edenworky opened 1 week ago
I haven't seen this issue before, and it's surprising to see the error message mention an unbound fn since profile
is a macro that ordinarily gets compiled into a no-op if you don't explicitly have profiling enabled.
Can you give me some more info about what version of instaparse you're using, what version of clout and compojure? Maybe show me the project.clj file if you're using lein. Bonus points if you have a minimal project that demonstrates the error for me to try on my system to better understand what is happening.
Sorry you ran into an issue, and I'll do what I can to help you track it down.
Does this happen at compile time or run time?
Hey, sorry, not with my laptop until tomorrow.
It happens in cider+eglot+lsp-clojure after running clean-ns
, using a
decently recent version of compojure, maybe 3 months old at most. It
happens a few seconds after the fact, just prints it in cider. Soo run
time? I imagine it happens in-REPL. (I'm not using clout directly, it's a
dependency of my version of compojure)
On Fri, 21 Jun 2024, 23:22 Mark Engelberg, @.***> wrote:
Does this happen at compile time or run time?
— Reply to this email directly, view it on GitHub https://github.com/Engelberg/instaparse/issues/234#issuecomment-2183402535, or unsubscribe https://github.com/notifications/unsubscribe-auth/ADRQMPTRGFASUFMGXGWRFITZISDSHAVCNFSM6AAAAABJWOC4QSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCOBTGQYDENJTGU . You are receiving this because you authored the thread.Message ID: @.***>
I'm using
instaparse
by way ofclout
by way ofcompojure
, I don't really understand the internal usage here, but I'm getting an error: