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

Compatibility check wrong for abstract type constructors #7234

Closed
vicuna opened this issue Apr 19, 2016 · 1 comment
Closed

Compatibility check wrong for abstract type constructors #7234

vicuna opened this issue Apr 19, 2016 · 1 comment
Assignees

Comments

@vicuna
Copy link

vicuna commented Apr 19, 2016

Original bug ID: 7234
Reporter: @stedolan
Assigned to: @garrigue
Status: closed (set by @xavierleroy on 2017-09-24T15:32:25Z)
Resolution: fixed
Priority: normal
Severity: crash
Fixed in version: 4.03.0+dev / +beta1
Category: typing
Related to: #6992
Monitored by: @gasche @yallop @hcarty

Bug description

OCaml version 4.03.0+dev19-2016-04-15

type (_, _) eq = Eq : ('a, 'a) eq | Neq : int -> ('a, 'b) eq

module F (T : sig type _ t end) = struct
let f (type a) (Neq n : (a, a T.t) eq) = n
end
module M = F (struct type 'a t = 'a end)
let _ = M.f Eq;;
Segmentation fault

The 'Eq' case should not be judged impossible, and the exhaustiveness check should fail but does not. This is a regression since 4.02.3, which correctly prints an exhaustivity warning and then raises Match_failure.

@vicuna
Copy link
Author

vicuna commented Apr 20, 2016

Comment author: @garrigue

Fixed in 4.03 and trunk by commits 06a0538 and a8a5da4.

New behavior is only not to add an equation when there is a contractiveness problem, so that both this PR and #6992 can be solved simultaneously (i.e., error message for #6992 changes)

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

No branches or pull requests

2 participants