From: "Christoph Höger" <christoph.hoeger@tu-berlin.de>
To: "François Pottier" <francois.pottier@inria.fr>,
"caml users" <caml-list@inria.fr>
Subject: Re: [Caml-list] ppx_deriving question: deferring code generation?
Date: Wed, 4 Jan 2017 14:53:10 +0100 [thread overview]
Message-ID: <c3c306e1-8171-a24f-3d05-5f22792a7d55@tu-berlin.de> (raw)
In-Reply-To: <9576980c-9aad-4af2-e512-dc9c42743cf2@inria.fr>
[-- Attachment #1.1: Type: text/plain, Size: 2484 bytes --]
Just out of curiosity, what does "vistors" do? If it resembles the usual
Visitor Pattern you might find my ppx_deriving_morphism useful:
https://github.com/choeger/ppx_deriving_morphism/
(either as a starting point or inspiration or as something to obsolete).
Am 04.01.2017 um 14:08 schrieb François Pottier:
>
> Hello all,
>
> I am currently in the process of writing a ppx_deriving plugin, called
> "visitors". Overall, this has been a pleasant experience; a few hundred
> lines
> of code have been sufficient to obtain nontrivial results.
>
> In normal use, the user writes something like this:
>
> type foo =
> Bar | Baz
> [@@deriving visitors]
>
> and some generated code is inserted just after the definition of the
> type foo.
>
> However, I have reached a situation where the generated code cannot be
> placed
> just after the type definition. That is, I need to allow user-written
> code to
> appear after the type definition and before the generated code.
>
> For instance, this user-written code could be a declaration of a global
> variable "x", whose type is "foo ref", and which the generated code
> uses. The
> declaration of "x" must appear after the definition of the type "foo",
> because
> the type of "x" mentions "foo". And the declaration of "x" must appear
> before
> the generated code, because the generated code (intentionally) refers to
> "x".
>
> I am imagining that perhaps the user could write something like this:
>
> type foo =
> Bar | Baz
> [@@deriving visitors { delayed = true }
>
> let x : foo option ref =
> ref None
>
> [@@visitors]
>
> The effect of the flag { delayed = true } would be to store the
> generated code
> somewhere in memory (instead of emitting right away), and the effect of the
> floating attribute [@@visitors] would be to fetch that code from memory and
> emit it.
>
> To me, this seems somewhat ugly, but workable. Does ppx_deriving offer a
> better approach? Does anyone have a better suggestion? Comments are
> appreciated.
>
> Best regards,
>
> --
> François Pottier
> francois.pottier@inria.fr
> http://gallium.inria.fr/~fpottier/
>
--
Christoph Höger
Technische Universität Berlin
Fakultät IV - Elektrotechnik und Informatik
Übersetzerbau und Programmiersprachen
Sekr. TEL12-2, Ernst-Reuter-Platz 7, 10587 Berlin
Tel.: +49 (30) 314-24890
E-Mail: christoph.hoeger@tu-berlin.de
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2017-01-04 13:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-04 13:08 François Pottier
2017-01-04 13:49 ` Gabriel Scherer
2017-01-04 15:37 ` François Pottier
2017-01-04 13:53 ` Christoph Höger [this message]
2017-01-04 15:58 ` François Pottier
2017-01-04 15:20 ` Alain Frisch
2017-01-04 16:04 ` François Pottier
2017-01-06 22:58 ` whitequark
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=c3c306e1-8171-a24f-3d05-5f22792a7d55@tu-berlin.de \
--to=christoph.hoeger@tu-berlin.de \
--cc=caml-list@inria.fr \
--cc=francois.pottier@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