Seems like a stretch, but is there a debug mode in which I can see typechecking errors pointed at a pretty-printed HIR rather than the original source spans? Some desugaring code I wrote is getting type mismatch errors, but it's hard to tell which part of the code they're coming from
@Taylor Cramer: I wonder if you could use
-Zunpretty=hir and then try compiling the output
@varkor unfortunately that doesn't work
@varkor in my case, the HIR compiles just fine XD
so it's some extra bit of metadata I'm setting that's causing it to fail
I would love it if we had something like that.
cc @WG-diagnostics we could probably add a mode where we don't highlight code spans but dump the pretty printed HIR (all levels of expansion even) of whatever span is offending the compiler