Totally agree! I have to say, as an author of preprocessor/compiler toolchains, I’ve struggled a lot with designing error reporting in a way that maintains abst

Totally agree! I have to say, as an author of preprocessor/compiler toolchains, I’ve struggled a lot with designing error reporting in a way that maintains abstractions in the toolchains, but still produces useful error messages. Oftentimes, I’ve fallen back to hard coding error messages that assume a particular code path. I’d be really interested in seeing examples of error reporting patterns that work well across multiple levels of abstraction.