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
Typing error with almost the same signature #6147
Comments
Comment author: @garrigue The error message is not strange: I do not know exactly while this input-output relation was not enforced |
Comment author: @lefessan I got a similar message once with trunk, it was caused by type annotations in the code. 4.01 propagates such type annotations, instead of just verifying that they are correct. I found that, by removing the type annotation (that was useless), the problem would go away. |
Comment author: jpdeplaix Ok, thanks. As for me, this is fixed (see here: ocsigen/ocsimore@663e47f) Note: I'm coping here the error, because the link may not be available later (for those who wants to see it): File "src/core/server/xform.ml", line 1: |
Comment author: @damiendoligez Setting target to "after-next" as this is not blocking for the 4.01.0 release. If you disagree, react quickly. |
Comment author: jpdeplaix It's ok. It's not really a bug and it's fixed for me, so, yes it's not blocking. |
Comment author: @garrigue Fabrice, your comment disturbs me. On the other hand, as I wrote in my previous comment, independently of the improved propagation, 4.01 is actually stricter (i.e. less polymorphic) than 4.00 for some constructs. It tries to stay closer to the specification. So this is certainly a plausible cause. |
Comment author: @garrigue Close this one, as the problem seems solved. |
Original bug ID: 6147
Reporter: jpdeplaix
Assigned to: @garrigue
Status: closed (set by @garrigue on 2014-04-04T05:24:15Z)
Resolution: not a bug
Priority: normal
Severity: major
Version: 4.01.0+beta/+rc
Target version: 4.01.1+dev
Category: typing
Bug description
Ocsimore (an eliom web site) is unable to compile with ocaml 4.01. It fails with a strange error message (see the following link). I tried to change the signature, but the wanted signature changed too and I abandoned.
So, sorry if I don't help that much, but at least I made a report.
Maybe someone can take a look at this.
Steps to reproduce
https://ci.inria.fr/ocsigen/view/4.01/job/Ocsimore-4.01/lastFailedBuild/console
The text was updated successfully, but these errors were encountered: