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
Explicit coercion in value bindings does not work in OCaml 5.1.0~alpha1 #12188
Milestone
Comments
This is a bug in #12119: I didn't catch the fact that coercions are allowed on value binding. I will have a fix shortly, and since it requires an update to the parsetree, I will publish another alpha to try to stabilize the intermediary representation during the alpha releases. |
Octachron
added a commit
to Octachron/ocaml
that referenced
this issue
Apr 18, 2023
Octachron
added a commit
to Octachron/ocaml
that referenced
this issue
Apr 18, 2023
Octachron
added a commit
to Octachron/ocaml
that referenced
this issue
May 24, 2023
Octachron
added a commit
that referenced
this issue
May 24, 2023
#12188: fix coercion in value bindings
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
compiles just fine with OCaml 5.0.0 but fails with OCaml 5.1.0~alpha1 with:
This behaviour can only be observed when the coercion is in the binding. When it is in the expression section it works fine:
The text was updated successfully, but these errors were encountered: