3 ms·
This mirrors my experience in SML/NJ, where for the longest time the most common error message the compiler would spit out was 'tycon mismatch' and a Google sea
by shadowgovt 4y ago
This mirrors my experience in SML/NJ, where for the longest time the most common error message the compiler would spit out was 'tycon mismatch' and a Google search would not tell you what a tycon was (it's a type constructor).
I think, unfortunately, I've observed a pattern in much functional programming (F# being a blessed exception) that relatively excellent computer language designers suffer from the utter ineptitude of the human language competency of the tool authors. These days, I am far more interested in an elegant tool chain and support infrastructure than an elegant language.
- eckza 4y agoIf you ever do any frontend work, you should give Elm a try. The tooling is lightweight but effective; and the compiler error messages are best-in-class.
- kopecs 4y agoSadly I think SML/NJ has some of the worst messages for SML; Poly/ML and MLton both end up with something more reasonable than the dreaded Error: operator and operand do not agree [tycon mismatch]