I've been looking at these slides about improving type error messages for programming languages.

One of the things they describe, starting at Slide 8, is the concept of amechanicity. Anytime the internals of a compiler, such as optimizations or de-sugaring are exposed, this is an example of mechanicity. A goal of quality error messages is to stay close to the source code, without leaking details of the compiler implementation to the programmer.

I can't find any references to this concept outside of these slides. Has anyone come across this before, particularly in a paper that would be more reliable to cite than lecture slides?

  • 2
    $\begingroup$ I've literally never heard that term before and I've read hundreds of papers on type theory and type systems and compiler implementation including papers focused on error messages. I'm pretty sure the term is idiosyncratic, though the idea behind it is certainly appreciated (as an ideal at least). $\endgroup$ – Derek Elkins Feb 5 '16 at 1:54

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.