News for hackers. Stuff that matters.
Re:The Easiest Way to Build a Type Checker by recursivecaveat on Sunday November 30, 2025 @02:43PM (#46099719)
Keep in mind one of the most important attributes of a good compiler is clearly explaining to the user what caused compilation failure and why. If you try to solve in a very abstract and general space it could be challenging to give an actionable error message.
Re:The Easiest Way to Build a Type Checker by Quekid5 on Sunday November 30, 2025 @03:01PM (#46099864)
Yup, that's basically it. "SAT says no" isn't a very useful error message.
Re:The Easiest Way to Build a Type Checker by saghm on Sunday November 30, 2025 @06:42PM (#46101651)
I suspect you've intentionally phrased this to avoid referencing type checking in particular, since this is also the main reason that mainstream programming languages tend to use hand-written parsers rather than generators from what I understand, and I imagine it applies to a lot of other features as well.