Custom type errors are great. The titular prefix not so much:
Compared to a regular error message:
Github told me to discuss this here. So I propose:
Get rid of “A custom type error occurred while solving type class constraints”.
Why should the user care about this?
And as somebody who went through the trouble of defining custom error messages, it’s disheartening to not have them front and centre.
Hm yeah, I think I was thinking about this the other day too. I think it’s useful to have some indication that it’s a custom type error besides seeing that noted in the error code (which few people look at). Just so people know that it’s an API decision, and not something built in to the compiler. But a less conspicuous indication of that would be good!
(P.S. I would have been fine with this as a compiler issue/PR directly.)
