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
As far as I understand, pattern-matching in getValueDefault is deconstructed as an if then else in which selectors appear. But according to #3070 selectors are partially-defined, leading to the error. This is regrettable as the original pattern-matching was fully-specified.
Do you think there is a chance that the Spacer CHC solver could support fully-specified pattern-matching? I know that I could use the workaround detailed in #3070, but my real case involves nested pattern-matching, and doing so will result in the introduction of hundreds variables, an extent that I would like to avoid...
The text was updated successfully, but these errors were encountered:
I am facing the following issue when using pattern-matching with the Spacer CHC solver:
As far as I understand, pattern-matching in
getValueDefault
is deconstructed as anif then else
in which selectors appear. But according to #3070 selectors are partially-defined, leading to the error. This is regrettable as the original pattern-matching was fully-specified.Do you think there is a chance that the Spacer CHC solver could support fully-specified pattern-matching? I know that I could use the workaround detailed in #3070, but my real case involves nested pattern-matching, and doing so will result in the introduction of hundreds variables, an extent that I would like to avoid...
The text was updated successfully, but these errors were encountered: