Skip to content

Handle errors in lazy-seqs at the root

Compare
Choose a tag to compare
@Olical Olical released this 20 May 19:07
· 1781 commits to master since this release
4a79ceb

So if you evaluated something that returned a lazy-seq that would throw when it was fully resolved it would cause an error that never displayed. This is because the error happens inside the actual internal prepl code, not inside my eval code where I try/catch. I've solved this with a doall before the pr-str which should prevent any of these in the future.

I added some more code to check for these unhandled errors in the future and log them with some information about it probably being a bug in Conjure, so you should report them if you see more!

This was raised in #33 and hopefully fixed in this patch.