I'm using shadow-cljs 2.12.7, re-frame/tracing 0.6.2.
I wanted to use fn-traced for all my events and noticed that the compilation suddenly kept my CPU busy indefinitely, I always had to kill the process. Then I was able to narrow it down to one event that used a loop, and indeed that was the one responsible.
With youthful recklessness and delusions of grandeur I looked through the code, hoping I could provide a PR and make new friends, but soon had to face reality: someone who knows what s/he is doing is needed.
At the same time I think it unlikely to be the first person to run into this, but maybe loops aren't so common in most event handlers?
Evening, folks.
I'm using shadow-cljs 2.12.7, re-frame/tracing 0.6.2.
I wanted to use
fn-traced
for all my events and noticed that the compilation suddenly kept my CPU busy indefinitely, I always had to kill the process. Then I was able to narrow it down to one event that used a loop, and indeed that was the one responsible.I can reproduce it with this:
The
recur
seems to be the culprit or at least a necessary abettor, because this is fine:With youthful recklessness and delusions of grandeur I looked through the code, hoping I could provide a PR and make new friends, but soon had to face reality: someone who knows what s/he is doing is needed.
At the same time I think it unlikely to be the first person to run into this, but maybe loops aren't so common in most event handlers?