it's difficult to debug macro logic without full exception, and this this is a new dialect so it wasn't obvious (to me at least!) that full exception wasn't being thrown
As another workaround I can also try/catch the error inside a macro, assuming in a given scenario i know where error originated and it was self defined
it's difficult to debug macro logic without full exception, and this this is a new dialect so it wasn't obvious (to me at least!) that full exception wasn't being thrown
i ended up running local version of ClojureDart and printing exception myself https://github.com/Tensegritics/ClojureDart/blob/595062ba49f0c6210aa7b69385b940386fab0872/clj/src/cljd/build.clj#L196-L202
I understand wanting to show prettier error messages, perhaps we can add a special debug flag? Happy to create PR after discussion