[WIP] upgrade to OCaml 5#199
Conversation
|
Hey @akabe One of the reasons should be following deprecations: Affected test cases:
Another reason is related to the toplevel change, and it doesn't accept
I've commented out these test cases and need your help on the details to fix these for OCaml 5. |
akabe
left a comment
There was a problem hiding this comment.
@kimmywork Thank you for creating a patch for OCaml 5. OCaml 5 had many disruptive changes and I skipped responding to them. I suggest ideas for solving the issue of Test_evaluation.test__directive and merlin.
| ] | ||
| depends: [ | ||
| "ocaml" {>= "4.10.0" & < "4.15"} | ||
| "ocaml" {(>= "4.10.0" & < "4.15") | (>= "5.0.0")} |
There was a problem hiding this comment.
I forget updating the restriction of ocaml versions. I'd like to suggest
"ocaml" {>= "4.10.0"}
because ocaml-jupyter kernel now supports 4.15.
cf. jupyter.2.8.2/opam
|
|
||
| let test__directive ctxt = | ||
| (* let test__directive ctxt = | ||
| let status, actual = eval "#load \"str.cma\" ;; Str.regexp \".*\"" in |
There was a problem hiding this comment.
This test case only checks whether a directive works fine, or not. We can check an other directive, not #load.
In my environment, this patch works.
-(* let test__directive ctxt =
- let status, actual = eval "#load \"str.cma\" ;; Str.regexp \".*\"" in
+let test__directive ctxt =
+ let status, actual = eval "#require \"str\" ;; Str.regexp \".*\"" in
let expected = [iopub_success ~count:0 "- : Str.regexp = <abstr>\n"] in| let actual = complete merlin code ~pos:15 in | ||
| require expected actual ~msg:"module" ; | ||
| require expected actual ~msg:"module" | ||
| (* ; |
There was a problem hiding this comment.
The commented-out lines are not important checks. Could you remove them?
| @@ -1,3 +1,3 @@ | |||
| (-w A-4-31-33-34-39-41-42-43-44-45-48-49-50-58-66 | |||
| -safe-string -strict-sequence -strict-formats | |||
| -safe-string -strict-sequence -strict-formats | |||
There was a problem hiding this comment.
Could you delete a space at the end of line?
|
The issue of ppx is hard maybe. I have not yet been able to find a solution. In the official OCaml 5, $ ocaml
OCaml version 5.0.0
# #require "ppx_deriving.show";;
/Users/akabe/.opam/5.0.0/lib/result: added to search path
/Users/akabe/.opam/5.0.0/lib/result/result.cma: loaded
/Users/akabe/.opam/5.0.0/lib/ppx_deriving/runtime: added to search path
/Users/akabe/.opam/5.0.0/lib/ppx_deriving/runtime/ppx_deriving_runtime.cma: loaded
/Users/akabe/.opam/5.0.0/lib/ppx_deriving: added to search path
/Users/akabe/.opam/5.0.0/lib/ppx_deriving/./ppx_deriving: activated
/Users/akabe/.opam/5.0.0/lib/ppx_deriving/show: added to search path
ppx_deriving: package:ppx_deriving.show: option added |
|
CI fails due to code format. Try |
Same on my side. I've fixed the code in your comments above, but just found another issue when running Full output: |
|
I see, all |
|
@kimmywork Thanks for fixing. I am also aware of the same issue. As it is likely a deep-rooted problem, I anticipate that it will take some time to find a solution, but I will continue my investigation as well. I have been a bit busy lately, so please give me some time. |
|
Has there been any progress on this issue? |
|
Thanks a lot for the work, closing this one as #210 was merged. |

No description provided.