Jarvis Carroll 5dcc05d56a Change fate_to_erlang warning
This warning always confuses me. Usually it is a case I haven't actually implemented,
but I don't need the program to diagnose that for me, I need the program to tell me what the
type was, so that I can work out why it thinks it isn't implemented.

All three terms of the annotated type are relevant, but the annotated version can only differ from the normalized version if
it is a record or variant definition, so we special case those two just to communicate that the fact that it is *some* kind of record
did successfully pass through to the coerce logic, and otherwise we just try and print the opaque and normalized types faithfully.
2026-05-12 06:00:26 +00:00
2026-05-10 19:35:20 +09:00
2026-05-10 17:56:34 +09:00
2025-04-16 16:07:45 +09:00
2026-05-12 06:00:26 +00:00
2026-05-10 19:35:20 +09:00
2024-03-27 14:45:50 +09:00
2024-03-27 14:45:50 +09:00
2026-05-10 17:56:34 +09:00
S
Description
No description provided
MIT 1.3 MiB
Languages
Erlang 100%