From: mukesh tiwari <mukeshtiwari.iiitm@gmail.com>
To: caml users <caml-list@inria.fr>
Subject: [Caml-list] Type Error in OCaml Code
Date: Fri, 14 Jan 2022 18:56:55 +0000 [thread overview]
Message-ID: <CAFHZvE_WWce5meetFg_O=VtQYwObtWXfBnw5O5GVKjc02dk5KA@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1162 bytes --]
Hi everyone,
My Coq project depends on a OCaml library [1] --the original library [2]--
which used to compile without any error in the past, but now it's no more.
If you run 'make all' in the ocaml-java directory, it throws an error '
*This expression has type Parsetree.pattern but an expression was
expected of type Migrate_parsetree.Ast_406.Parsetree.pattern' *
Could someone please tell me how to get rid of this error? (To me it seems
like some code restructuring in ocaml-migrate-parsetree).
Best,
Mukesh
ocaml-java git:(master) ✗ make all
File "ppx/ast_tools.ml", line 31, characters 36-55:
31 | let mk_let id expr = [%stri let [%p Pat.var (mk_loc id)] = [%e expr]]
^^^^^^^^^^^^^^^^^^^
Error:
*This expression has type Parsetree.pattern but an expression was
expected of type Migrate_parsetree.Ast_406.Parsetree.pattern*
make[1]: *** [bin/ppx/ast_tools.cmo] Error 2
make: *** [bin/ocaml-java-ppx] Error 2
[1]
https://github.com/mukeshtiwari/EncryptionSchulze/tree/master/code/Workingcode/ocaml-java
[2] https://github.com/Julow/ocaml-java/
[-- Attachment #2: Type: text/html, Size: 1617 bytes --]
next reply other threads:[~2022-01-14 18:57 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-14 18:56 mukesh tiwari [this message]
2022-01-15 21:18 ` Nicolás Ojeda Bär
2022-01-16 9:40 ` [Caml-list] Ask questions on the mailing lists too orbifx
2022-01-16 14:31 ` Sam Kuper
2022-01-17 9:20 ` Sébastien Hinderer
2022-01-17 9:33 ` Daniil Baturin
2022-01-17 14:30 ` Sam Kuper
2022-01-17 14:56 ` Daniil Baturin
2022-01-17 17:36 ` Sam Kuper
2022-01-17 21:06 ` Gabriel Scherer
2022-01-18 1:51 ` Sam Kuper
2022-01-19 15:46 ` Sébastien Hinderer
2022-01-18 9:48 ` orbifx
2022-01-18 15:55 ` Simon Cruanes
2022-01-19 16:31 ` Sébastien Hinderer
2022-01-19 17:51 ` Sam Kuper
2022-01-19 18:09 ` Sam Kuper
2022-01-19 19:09 ` Sébastien Hinderer
2022-01-19 20:53 ` Sam Kuper
2022-01-19 18:42 ` Simon Cruanes
2022-01-19 19:03 ` Sébastien Hinderer
2022-01-19 20:50 ` Sam Kuper
2022-01-20 20:56 ` Edwin Török
2022-03-11 8:46 ` Sébastien Hinderer
2022-03-11 9:37 ` Vasilis Goumas
2022-03-11 9:42 ` Gabriel Scherer
2022-01-19 15:33 ` Sébastien Hinderer
2022-01-19 21:43 ` Gabriel Scherer
2022-01-19 22:01 ` Sam Kuper
2022-01-19 22:38 ` Sébastien Hinderer
[not found] ` <50AF4FEF-5CD6-40E7-9FA3-78814CBEE230@etorok.eu>
2022-01-17 22:47 ` Sam Kuper
2022-01-17 9:53 ` Alan Schmitt
2022-01-17 13:52 ` Sam Kuper
2022-01-19 15:18 ` Sébastien Hinderer
2022-01-19 15:54 ` Sébastien Hinderer
2022-01-20 9:12 ` Alan Schmitt
[not found] ` <87pmom7sz7.fsf@m4x.org>
2022-01-20 14:15 ` Sébastien Hinderer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAFHZvE_WWce5meetFg_O=VtQYwObtWXfBnw5O5GVKjc02dk5KA@mail.gmail.com' \
--to=mukeshtiwari.iiitm@gmail.com \
--cc=caml-list@inria.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox