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

as ignored on types containing universal variables #6745

Closed
vicuna opened this issue Jan 8, 2015 · 5 comments
Closed

as ignored on types containing universal variables #6745

vicuna opened this issue Jan 8, 2015 · 5 comments
Assignees

Comments

@vicuna
Copy link

vicuna commented Jan 8, 2015

Original bug ID: 6745
Reporter: @lpw25
Assigned to: @garrigue
Status: assigned (set by @garrigue on 2015-11-30T08:46:58Z)
Resolution: open
Priority: normal
Severity: minor
Category: typing
Monitored by: @hcarty

Bug description

It seems that an as constraint on a type containing a univar is silently ignored:

# type 'a r = { x: 'b. 'b list as 'a };;
type 'a r = { x : 'b. 'b list; }

compared to:

# type 'a r = { x: 'b. int list as 'a };;
type 'a r = { x : 'a; } constraint 'a = int list
@vicuna
Copy link
Author

vicuna commented Nov 30, 2015

Comment author: @garrigue

I have opened a pull-request:
#322

However, it is not easy to get the right behavior without breaking symmetry, or requiring multiple passes on the whole syntax tree (as in SML).
Maybe this should rather go with a rework of type variable scope.

@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 11, 2020
@lpw25
Copy link
Contributor

lpw25 commented May 11, 2020

This is still an issue

@github-actions github-actions bot removed the Stale label Jun 15, 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 Jun 16, 2021
@gasche gasche removed the Stale label Jun 16, 2021
@github-actions
Copy link

github-actions bot commented Jul 6, 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 Jul 6, 2022
@github-actions github-actions bot closed this as completed Aug 8, 2022
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

4 participants