From: "François Pottier" <francois.pottier@inria.fr>
To: Gabriel Scherer <gabriel.scherer@gmail.com>
Cc: Peter Zotov <whitequark@whitequark.org>, caml users <caml-list@inria.fr>
Subject: Re: [Caml-list] ppx_deriving question: deferring code generation?
Date: Wed, 4 Jan 2017 16:37:41 +0100 [thread overview]
Message-ID: <78c6cc72-a165-dff1-2ed3-3afa66088ef0@inria.fr> (raw)
In-Reply-To: <CAPFanBFfXpF-G9DK7io8c0hR2DT2rA=DwK8F0pC5Ffw7HvHFmg@mail.gmail.com>
Hello Gabriel,
On 04/01/2017 14:49, Gabriel Scherer wrote:
> (If we had access to the type-checking environment,
Indeed, that is the question. As far as I understand, the whole ppx
system today is purely syntactic, and there is no way of looking up
the definition of a type. Or is there?
--
François Pottier
francois.pottier@inria.fr
http://gallium.inria.fr/~fpottier/
next prev parent reply other threads:[~2017-01-04 15:37 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 [this message]
2017-01-04 13:53 ` Christoph Höger
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=78c6cc72-a165-dff1-2ed3-3afa66088ef0@inria.fr \
--to=francois.pottier@inria.fr \
--cc=caml-list@inria.fr \
--cc=gabriel.scherer@gmail.com \
--cc=whitequark@whitequark.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