Closed snocl closed 6 years ago
Acking this, will be looking into it in the next day or two.
Looks like there's a bug expanding wildcards over nested tuples. I think we're treating the inner tuple as having one element. A fix is pending.
As a temporary workaround, you should be able to expand out the wildcards:
match ((0, 1), 2)
| ...:
| ((_, _), _): ...
;;
I ran into some weird behavior when matching on tuples containing tuples.
Differing patterns considered conflicting:
Match with catch-all pattern considered nonexhaustive:
In both cases, the order of the elements is significant; the following cases compile without error:
I tested this on the most recent version of master,
ebbdfc2
.