Open NPCRUS opened 1 month ago
This is somewhat typical for an error message when a derivation fails. I haven't spent a lot of time investigating solutions yet, but one option may be to implement derivation with a macro which calls into the existing code, but identifies the case where derivation fails (for any reason, including the above) and then goes through some steps to try to diagnose it, replacing the long inline error message with something more useful.
Assuming I want to only implement type class for Products, therefore I deliberately leave
split
method unimplemented. When trying to derive type class for Sum type - I get extremely cryptic message:I wonder if it can be improved somehow how to reproduce: