caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: "Nicolás Ojeda Bär" <nicolas.ojeda.bar@lexifi.com>
To: caml users <caml-list@inria.fr>,
	mukesh tiwari <mukeshtiwari.iiitm@gmail.com>
Subject: RE: [Caml-list] Type Error in OCaml Code
Date: Sat, 15 Jan 2022 21:18:56 +0000	[thread overview]
Message-ID: <PAZP264MB2848FE1F1B8B4FA8A6D09ECDC3559@PAZP264MB2848.FRAP264.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <CAFHZvE_WWce5meetFg_O=VtQYwObtWXfBnw5O5GVKjc02dk5KA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2109 bytes --]

Dear Mukesh,

The solution of your problem is probably: "update the library and all its dependencies to the latest version of ppxlib/ocaml-migrate-parsetree." Unfortunately, churn in the ppx ecosystem has been a problem since the beginning (though I believe some steps have been taken recently to mitigate this issue).

For more specific help I encourage you to ask your question on Discuss https://discuss.ocaml.org/ (which I saw you have already done!).

Cheers,
Nicolas
________________________________
De : caml-list-request@inria.fr <caml-list-request@inria.fr> de la part de mukesh tiwari <mukeshtiwari.iiitm@gmail.com>
Envoyé : vendredi 14 janvier 2022 19:56
À : caml users <caml-list@inria.fr>
Objet : [Caml-list] Type Error in OCaml Code


CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.


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<http://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: 5032 bytes --]

  reply	other threads:[~2022-01-15 21:19 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-14 18:56 mukesh tiwari
2022-01-15 21:18 ` Nicolás Ojeda Bär [this message]
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=PAZP264MB2848FE1F1B8B4FA8A6D09ECDC3559@PAZP264MB2848.FRAP264.PROD.OUTLOOK.COM \
    --to=nicolas.ojeda.bar@lexifi.com \
    --cc=caml-list@inria.fr \
    --cc=mukeshtiwari.iiitm@gmail.com \
    /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;
as well as URLs for NNTP newsgroup(s).