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

unterminating type checking for recursive modules #3674

Open
vicuna opened this issue Jun 7, 2005 · 7 comments
Open

unterminating type checking for recursive modules #3674

vicuna opened this issue Jun 7, 2005 · 7 comments
Labels
feature-wish known-limitation Acknowledge the problem, but there is no plan to fix it recursive-modules typing wontfix

Comments

@vicuna
Copy link

vicuna commented Jun 7, 2005

Original bug ID: 3674
Reporter: administrator
Status: acknowledged
Resolution: won't fix
Priority: normal
Severity: feature
Target version: later
Category: typing
Tags: recmod
Related to: #3935
Monitored by: "Julien Signoles" "Keiko NAKATA"

Bug description

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

Type checking does not terminate against the following program:

module type M = sig 
    module rec F : functor (X : sig type t end) -> sig type t = F(F(X)).t end
@vicuna
Copy link
Author

vicuna commented Jul 29, 2005

Comment author: administrator

Tough example. Will not fix in 3.08.

@vicuna
Copy link
Author

vicuna commented Sep 11, 2012

Comment author: @damiendoligez

Still present in 4.00.1+dev

@vicuna
Copy link
Author

vicuna commented Dec 4, 2015

Comment author: runhang

I am very interesting in why type checking this code will not terminate. Would someone like to spare some time to give a basic explanation?

@vicuna
Copy link
Author

vicuna commented Mar 15, 2017

Comment author: @garrigue

Move it to feature since we have no way to solve this with the current approach.

@github-actions
Copy link

This issue has been open one year with no activity. Consequently, it is being marked with the "stale" label. What this means is that the issue will be automatically closed in 30 days unless more comments are added or the "stale" label is removed. Comments that provide new information on the issue are especially welcome: is it still reproducible? did it appear in other contexts? how critical is it? etc.

@github-actions github-actions bot added the Stale label May 18, 2020
@garrigue garrigue added known-limitation Acknowledge the problem, but there is no plan to fix it and removed Stale labels May 18, 2020
@github-actions
Copy link

This issue has been open one year with no activity. Consequently, it is being marked with the "stale" label. What this means is that the issue will be automatically closed in 30 days unless more comments are added or the "stale" label is removed. Comments that provide new information on the issue are especially welcome: is it still reproducible? did it appear in other contexts? how critical is it? etc.

@github-actions github-actions bot added the Stale label Oct 18, 2021
@garrigue garrigue removed the Stale label Oct 20, 2021
@github-actions
Copy link

github-actions bot commented Nov 2, 2022

This issue has been open one year with no activity. Consequently, it is being marked with the "stale" label. What this means is that the issue will be automatically closed in 30 days unless more comments are added or the "stale" label is removed. Comments that provide new information on the issue are especially welcome: is it still reproducible? did it appear in other contexts? how critical is it? etc.

@github-actions github-actions bot added the Stale label Nov 2, 2022
@garrigue garrigue removed the Stale label Nov 2, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature-wish known-limitation Acknowledge the problem, but there is no plan to fix it recursive-modules typing wontfix
Projects
None yet
Development

No branches or pull requests

3 participants