You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now the #lang gibboncase expressions are very fragile. They require exhaustive pattern matches and I think they even require the same order as in the data definition.
This can be relaxed by adding a pass early in the compiler pipeline which:
puts the cases in a canonical order (if that's really needed... but in any case it doesn't hurt)
replaces all missing cases with errors
The text was updated successfully, but these errors were encountered:
There's still the issue of handling incomplete pattern matches.
This can be accomplished by an L0->L0 pass that inspects case expressions and adds appropriate MISSING_PATTERN -> error alternatives and prints a warning during compilation.
Right now the
#lang gibbon
case
expressions are very fragile. They require exhaustive pattern matches and I think they even require the same order as in the data definition.This can be relaxed by adding a pass early in the compiler pipeline which:
The text was updated successfully, but these errors were encountered: