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
[github patch] warn user when a type variable in a type constraint has been instantiated #6313
Comments
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. |
This still sounds like an excellent idea to me. Would people that know about the type-check be able to tell whether the patch was correct and still makes sense? (cc @garrigue @lpw25 @trefis @let-def). I think that if we wanted to gather consensus on this, we would need to ensure that people that use the feature for something else than instantiation have a way to avoid the warning. I believe that |
Using |
We need a syntax for (1) a variable that may or may not be instantiated and generalizable (this is what people typically use |
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. |
Original bug ID: 6313
Reporter: @gasche
Status: acknowledged (set by @damiendoligez on 2014-07-16T13:08:38Z)
Resolution: open
Priority: normal
Severity: feature
Version: 4.02.0+dev
Category: typing
Tags: patch
Bug description
Reported by Grégoire Henry:
#6
Patch is available at:
https://github.com/ocaml/ocaml/pull/6.patch
The text was updated successfully, but these errors were encountered: