Is there a video or any other material accompanying the library?

Hi, I’m the author of the library 😃 Just added a demo image to the README.

Awesome, thanks!

is it stable already? (not beta)

I know it is in the code but how are you doing “clojure” version?

It’s still a work in progress. Still needs some work before the release.

> how are you doing “clojure” version? Sorry, but I don’t get what you mean.

Who knows, if this gets really good, maybe we can see it integrated into Clojure itself. I know I could’ve used this when just starting out.

Very cool project, thanks for sharing, and thank you athos for developing it

If you overwrite clojure.main/repl-caught like (alter-var-root #'clojure.main/repl-caught (constantly st/pst-for)) in your user.clj, you can get this rich error info as the default error message on the REPL.

looks really cool, definitely giving this a try!

Yeah, that's pretty awesome

Neat! The formatting reminds me a bit of how shadow-cljs reports compile-time issues (example https://shadow-cljs.github.io/docs/UsersGuide.html#infer-externs):

------ WARNING #1 --------------------------------------------------------------
 File: ~/project/src/demo/thing.cljs:23:3
--------------------------------------------------------------------------------
  21 |
  22 | (defn wrap-baz [x]
  23 |   (.baz x))
---------^----------------------------------------------------------------------
 Cannot infer target type in expression (. x baz)
--------------------------------------------------------------------------------

@U0508956F what are the mechanics of this? curious if i can get an equivalent thing working for plain ol’ java

@U3JH98J4R It's not that hard for Clojure. Clojure source code is just a resource on the classpath. You can read it just as an ordinary resource file (That's what clojure.repl/source does internally). But, I think it would require more to do the same thing for Java. You might have to decompile the bytecode to support third-party libraries.

This is really nice, probably a great way to improve errors, instead of fixing the message, just show the actual code fragments that threw the error

Nice idea!

Thanks! Yeah, I started dogfooding the library at work last week, and it help me a lot already.