From: "Daniel Bünzli" <daniel.buenzli@erratique.ch>
To: "Petter A. Urkedal" <paurkedal@gmail.com>
Cc: caml users <caml-list@inria.fr>
Subject: Re: [Caml-list] Terser ppx syntax for common usage (like monads)
Date: Sat, 10 Oct 2015 15:09:09 +0100 [thread overview]
Message-ID: <F139F045CACC49BB99932C6BFF5C389F@erratique.ch> (raw)
In-Reply-To: <CALa9pHQAfTjbQ-adr29QYoEtT=zgEywa9+btSuWRFc==w-giHQ@mail.gmail.com>
> Now, that's not necessarily a bad thing, but the monad bind operation
> tends to be quite invasive, so I'd like to suggest adding a shorter
> syntax which the user could choose to map to their most pervasive ppx
> rewriter.
This entails that I can't possibly have an idea of what the code is doing without looking up what the build system is doing which is annoying. We should aim for self-describing sources rather than put too much knowledge in the build systems — which also means that usage of pre-processors should be frown upon in general.
Daniel
next prev parent reply other threads:[~2015-10-10 14:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-10 13:48 Petter A. Urkedal
2015-10-10 13:57 ` Petter A. Urkedal
2015-10-10 14:09 ` Daniel Bünzli [this message]
2015-10-10 17:32 ` Petter A. Urkedal
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=F139F045CACC49BB99932C6BFF5C389F@erratique.ch \
--to=daniel.buenzli@erratique.ch \
--cc=caml-list@inria.fr \
--cc=paurkedal@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