is there a methodical approach to implementing tools that check rules, e.g. type checkers/compilers, in a way that makes it is easy to surface *why* a certain result was achieved? e.g. why you're getting a "expected type A, found type B"
Conversation
not necessarily in a user-friendly way, as I think that is an upper layer of translating why an error happened so that it is friendly for a user. more like what a developer writing the error message needs to have access to while implementing it
3
2
This Tweet was deleted by the Tweet author. Learn more
do you have examples? I can understand that it depends, but I'm interested anyways
This Tweet was deleted by the Tweet author. Learn more
You’re unable to view this Tweet because this account owner limits who can view their Tweets. Learn more
