Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

GADT exhaustiveness check is still broken #5906

vicuna opened this issue Jan 24, 2013 · 1 comment

GADT exhaustiveness check is still broken #5906

vicuna opened this issue Jan 24, 2013 · 1 comment


Copy link

@vicuna vicuna commented Jan 24, 2013

Original bug ID: 5906
Reporter: @sbriais
Assigned to: @garrigue
Status: closed (set by @garrigue on 2013-01-25T04:30:16Z)
Resolution: fixed
Priority: normal
Severity: minor
Platform: AMD64
OS: Linux
Version: 4.00.1
Fixed in version: 4.00.2+dev
Category: typing
Child of: #5998
Monitored by: @hcarty

Bug description

The attached file should warn that a pattern-matching is not exhaustive but does not.
The bug still exists in the current trunk (r13274).

File attachments

Copy link

@vicuna vicuna commented Jan 25, 2013

Comment author: @garrigue

Fixed in trunk and 4.00, at revisions 13276 and 13277.

There was a stupid bug in try_many_gadt.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
3 participants