From: Gabriel Scherer <gabriel.scherer@gmail.com>
To: "Emilio Jesús Gallego Arias" <e@x80.org>,
"Christoph Höger" <christoph.hoeger@celeraone.com>,
"OCaml Mailing List" <caml-list@inria.fr>
Subject: Re: [Caml-list] visitors.ppx and ppx_metaquot
Date: Fri, 6 Oct 2017 15:15:34 +0200 [thread overview]
Message-ID: <CAPFanBGE9QmUhzDbsxjwd_gSRCJOFXvJh_q_jGc8V-R+CCgK_Q@mail.gmail.com> (raw)
In-Reply-To: <874lrcu1ax.fsf@x80.org>
[-- Attachment #1: Type: text/plain, Size: 1108 bytes --]
I think that similar issues have been reported before, and seem to arise
out of a wrong interaction between ppx_deriving and ppx_type_conv:
https://github.com/ocaml-ppx/ppx_deriving/issues/149
https://github.com/janestreet/ppx_type_conv/issues/9
(Note: Jérémie Dimino, which has been handling most of the ppx_type_conv
maintenance, is currently in well-deserved holidays, so the safest bet for
the next couple months may indeed be to pin back to older versions that
work for you.)
On Fri, Oct 6, 2017 at 10:29 AM, Emilio Jesús Gallego Arias <e@x80.org>
wrote:
> Dear Christoph,
>
> Christoph Höger <christoph.hoeger@celeraone.com> writes:
>
> > Does anyone know a workaround?
>
> I had a similar problem [but not with visitors] that I solved by pinning
> ppx_deriving to the 4.1 version. I guess you lose little by not trying.
>
> E.
>
> --
> Caml-list mailing list. Subscription management and archives:
> https://sympa.inria.fr/sympa/arc/caml-list
> Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
> Bug reports: http://caml.inria.fr/bin/caml-bugs
[-- Attachment #2: Type: text/html, Size: 2005 bytes --]
prev parent reply other threads:[~2017-10-06 13:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-05 13:30 Christoph Höger
2017-10-06 8:29 ` Emilio Jesús Gallego Arias
2017-10-06 13:15 ` Gabriel Scherer [this message]
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=CAPFanBGE9QmUhzDbsxjwd_gSRCJOFXvJh_q_jGc8V-R+CCgK_Q@mail.gmail.com \
--to=gabriel.scherer@gmail.com \
--cc=caml-list@inria.fr \
--cc=christoph.hoeger@celeraone.com \
--cc=e@x80.org \
/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).