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

type checking a type path #3738

Closed
vicuna opened this issue Jul 27, 2005 · 2 comments
Closed

type checking a type path #3738

vicuna opened this issue Jul 27, 2005 · 2 comments
Labels

Comments

@vicuna
Copy link

vicuna commented Jul 27, 2005

Original bug ID: 3738
Reporter: administrator
Status: closed
Resolution: fixed
Priority: normal
Severity: minor
Category: ~DO NOT USE (was: OCaml general)

Bug description

Full_Name: NAKATA keiko
Version: 3.08.2
OS: freebsd
Submission from: orion.kurims.kyoto-u.ac.jp (130.54.16.5)

The following type definition for t does not type check.

module M = struct type t end

module F(X:sig type t end)(Y:sig type t = X.t end) = struct type t = int end

type t = F(M)(M).t

Observe that when I change the definition of M as

module M = struct type t = int end

it becomes well-typed.

@vicuna
Copy link
Author

vicuna commented Jul 27, 2005

Comment author: administrator

The following type definition for t does not type check.

module M = struct type t end

module F(X:sig type t end)(Y:sig type t = X.t end) = struct type t = int end

type t = F(M)(M).t

Thank you for this interesting bug report. It will be fixed shortly
in the 3.08 branch. In case you are wondering, it was due to a lack
of strengthening of the signature of M when type-checking the second
application (that of F(M) to M).

Regards,

  • Xavier Leroy

@vicuna
Copy link
Author

vicuna commented Jul 27, 2005

Comment author: administrator

Fixed in 3.08.4 by XL, 2005-07-27

@vicuna vicuna closed this as completed Jul 27, 2005
@vicuna vicuna added the bug label Mar 19, 2019
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

1 participant