Clojurians Log v2

👋 good morning, looking into errors today. I noticed a couple of cases where stacktraces are missing or (maybe) missing information, not sure if they are bugs / expected / etc.

@mhuebert 👋

the throw case might be easily fixable - not sure about the anonymous function one, but could be worth investigating

can you make separate issues about each?

I can point you a bit where to look, if you're interested in looking into it

I may have time - have to prioritize the final weeks of the Clojurists Together term, I’d like to have some kind of deliverable although there’s a huge surface area remaining 😅

no worries, if you can make the issue, then I will get to it eventually. this doesn't seem like a huge priority, but a nice to have, right?

yeah, it’s not the biggest thing. One interesting thing I’m thinking about is how I can resolve “stack frames” back to individual blocks that have been evaluated. Right now everything will be <expr>:1:x or whatever, relative to the block it was evaluated in. I’m not even sure how to phrase the question, but do you know if there’s any way I can pass some context to eval that would be included in the call stack / error metadata somehow?

or set the starting line/column

eg “eval this string, it is within a doc at position L3 C4”

There is :clojure.core/eval-file that you can set on the expression

I think clerk uses that too, SCI supports it as well

ah great

is there a way to set that other than modifying the string?

you can also do this:

(sci/binding [sci/file ...] (eval-string* ...))

i’m already using sci/eval-form maybe I can just do with-meta on the form

yes

ah perfect