Why don't you use GHC's Custom Type Error? #26
Description
The mechanism of indicating error using Elaborate type family is quite cool but now that extensible doesn't support older GHC, it can use GHC.TypeError to show more readable error messages. How do you think of it?
Example: I experimentally implemented it and found it useful when I can't remember the name of the field.
