jank reimagines C++ errors and gets an official native package repo

Welcome back! It's been three months since my last post and the amount of improvements to jank are staggering. Let me tell you all about it! Before jumping into the details, though, I want to say thank you to my Github sponsors and to…

From the article

Welcome back! It's been three months since my last post and the amount of improvements to jank are staggering. Let me tell you all about it! Before jumping into the details, though, I want to say thank you to my Github sponsors and to Clojurists Together for sponsoring me this whole year. Thank you! Error reporting Last year, I published a post showcasing how jank has reimagined Clojure errors. In every way, I aim for jank compiler errors to be more helpful, provide more context, and be more visually appealing than the Clojure JVM counterpart. Even in complex scenarios involving macros, jank excels. However, I hadn't yet tackled a couple of other areas of error reporting: runtime exceptions and C++ interop errors. Uncaught runtime exceptions In today's modern C++ compilers, there's no…

Share this resource