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
The "and redundancy" in the title makes it sound like refutation cases are something defined elsewhere, and have some relationship to GADTs via redundancy. The fact that redundancy isn't mentioned anywhere in the section is also confusing -- I think it means branches of a pattern match which are redundant due to being untypable. "which are both untypable" would be clarified by adding "because deep expects a [char t]".
Original bug ID: 7613
Reporter: coventry
Assigned to: @Octachron
Status: resolved (set by @Octachron on 2018-04-01T14:04:53Z)
Resolution: fixed
Priority: low
Severity: minor
Fixed in version: 4.07.0+dev/beta2/rc1/rc2
Category: documentation
Bug description
Currently this section: https://caml.inria.fr/pub/docs/manual-ocaml/extn.html#sec241
The "and redundancy" in the title makes it sound like refutation cases are something defined elsewhere, and have some relationship to GADTs via redundancy. The fact that redundancy isn't mentioned anywhere in the section is also confusing -- I think it means branches of a pattern match which are redundant due to being untypable. "which are both untypable" would be clarified by adding "because deep expects a [char t]".
My confusion was cleared up by https://discuss.ocaml.org/t/matching-incompatible-gadt-constructors/682 , FWIW. I think it's much clearer.
The text was updated successfully, but these errors were encountered: