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

Fatal error: exception Assert_failure("typing/ctype.ml", 1518, 10) #3909

Closed
vicuna opened this issue Dec 5, 2005 · 3 comments
Closed

Fatal error: exception Assert_failure("typing/ctype.ml", 1518, 10) #3909

vicuna opened this issue Dec 5, 2005 · 3 comments
Assignees
Labels

Comments

@vicuna
Copy link

vicuna commented Dec 5, 2005

Original bug ID: 3909
Reporter: abergou
Assigned to: @garrigue
Status: closed (set by @xavierleroy on 2006-08-01T01:09:04Z)
Resolution: fixed
Priority: normal
Severity: crash
Version: 3.08.3
Category: ~DO NOT USE (was: OCaml general)

Bug description

the attached code produces an assert failure...
(ocaml 3.08.3, Debian testing/GNU Linux)

it used to typecheck correctly about a year ago.

--
Damien Pous
Damien.Pous@ens-lyon.fr
(I am afraid there was no explicit way to give my email, so that you contact
me if necessary; while in anonymous mode...)

File attachments

@vicuna
Copy link
Author

vicuna commented Dec 5, 2005

Comment author: anonymous

I cannot myself check with 3.09...
However it seems the problem remains
(no "assertion failure" but something like "method color not found")

@vicuna
Copy link
Author

vicuna commented Dec 5, 2005

Comment author: @garrigue

Indeed, this did typecheck in 3.08.2 (fixing small typos.)
Unfortunately variances were unsound, so this had to be changed afterwards.

The modified version objets_damien2.ml typechecks on 3.09.0,
by adding explicit variance annotations.

I see 2 problems here:

  • this mysterious failure in the non-generalizable case
  • the spurious need for variance annotations

Jacques

@vicuna
Copy link
Author

vicuna commented Dec 5, 2005

Comment author: @garrigue

The first point is now fixed in the CVS version, branch release309.
This was just a wrong assertion in Ctype.unify3.

The second point would require a deep analysis of constraints.

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

No branches or pull requests

2 participants