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

Assert_failure("typing/ctype.ml", 359, 6) #6123

Closed
vicuna opened this issue Aug 6, 2013 · 3 comments
Closed

Assert_failure("typing/ctype.ml", 359, 6) #6123

vicuna opened this issue Aug 6, 2013 · 3 comments
Assignees
Milestone

Comments

@vicuna
Copy link

@vicuna vicuna commented Aug 6, 2013

Original bug ID: 6123
Reporter: @whitequark
Assigned to: @garrigue
Status: closed (set by @xavierleroy on 2015-12-11T18:23:54Z)
Resolution: fixed
Priority: normal
Severity: crash
Version: 4.00.1
Target version: 4.01.1+dev
Fixed in version: 4.01.0+dev
Category: typing
Related to: #5619

Bug description

While trying to compile the attached module, typechecker fails an assertion. The module is not well-typed; on 3.x this results in a type error.

Steps to reproduce

ocamlc ssa.ml

File attachments

@vicuna
Copy link
Author

@vicuna vicuna commented Aug 6, 2013

Comment author: @gasche

The code fails with a typing error as expected on 3.12. I reproduced the assert failure in both 4.00.1 and trunk.

@vicuna
Copy link
Author

@vicuna vicuna commented Aug 12, 2013

Comment author: @garrigue

This is apparently a consequence of the way #5619 was fixed.
Still looking for an alternative solution.

@vicuna
Copy link
Author

@vicuna vicuna commented Aug 20, 2013

Comment author: @garrigue

Fixed in trunk and 4.01, revisions 14021 an 14022.

@vicuna vicuna closed this Dec 11, 2015
@vicuna vicuna added the typing label Mar 14, 2019
@vicuna vicuna added this to the 4.01.1 milestone Mar 14, 2019
@vicuna vicuna added the bug label Mar 20, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants