From: Drup <drupyog+caml@zoho.com>
To: Alain Frisch <alain@frisch.fr>, Jun Furuse <jun.furuse@gmail.com>,
oleg@okmij.org, caml-list <caml-list@inria.fr>
Subject: Re: [Caml-list] [ANN] ppx_monadic.1.0.2, ppx for monadic do, pattern
Date: Mon, 19 Jan 2015 22:52:59 +0100 [thread overview]
Message-ID: <54BD7CBB.50409@zoho.com> (raw)
In-Reply-To: <54BCC6D6.6020702@frisch.fr>
> I can appreciate that authors of tools that requires special syntactic
> support would love to have their new forms look completely native to
> users, but the counter-argument can be made that keeping an explicit
> syntax (through the '%' character) for features that are not part of
> the official language is a good property. (Camlp4/campl5 are still
> available for people who want to play with the concrete syntax.)
I personally like the explicitness of the syntax a lot. The only issue
in OCaml currently is that, given the need for retro compatibility, it
goes sometimes against the terseness. For example the impossibility to
do " x@foo" instead of "x[@foo]". That's unavoidable, though.
This is, by the way, a point I dislike a lot with ppx_monadic. It abuses
the native syntax in completely alien ways and without annotations.
I like ppx_monad's syntax quite better due to the fact that it's always
explicitly a ppx (thanks to %monad) and do not overload the "do_"
identifier.
next prev parent reply other threads:[~2015-01-19 21:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-13 14:23 [Caml-list] [ANN] ppx_monadic.1.0.2, ppx for monadic do, pattern guards and monadic comprehension Jun Furuse
2015-01-14 8:40 ` [Caml-list] [ANN] ppx_monadic.1.0.2, ppx for monadic do, pattern oleg
2015-01-18 14:47 ` Jun Furuse
2015-01-19 7:33 ` [Caml-list] [ANN] ppx_monadic.1.0.2, ppx for monadic do, oleg
2015-01-19 8:34 ` Alain Frisch
2015-01-19 9:06 ` Gabriel Scherer
2015-01-19 9:40 ` Alain Frisch
2015-01-19 16:10 ` Jeremy Yallop
2015-01-19 8:56 ` [Caml-list] [ANN] ppx_monadic.1.0.2, ppx for monadic do, pattern Alain Frisch
2015-01-19 21:52 ` Drup [this message]
2015-01-20 3:53 ` Jun Furuse
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=54BD7CBB.50409@zoho.com \
--to=drupyog+caml@zoho.com \
--cc=alain@frisch.fr \
--cc=caml-list@inria.fr \
--cc=jun.furuse@gmail.com \
--cc=oleg@okmij.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