From: Gabriel Scherer <gabriel.scherer@gmail.com>
To: Alain Frisch <alain@frisch.fr>
Cc: oleg@okmij.org, Jun Furuse <jun.furuse@gmail.com>,
caml users <caml-list@inria.fr>
Subject: Re: [Caml-list] [ANN] ppx_monadic.1.0.2, ppx for monadic do,
Date: Mon, 19 Jan 2015 10:06:43 +0100 [thread overview]
Message-ID: <CAPFanBF4n2C8nRn9aDuWRLpnN04xxiTKYYPYmcr-Ar=L_tgVMA@mail.gmail.com> (raw)
In-Reply-To: <54BCC17A.4000802@frisch.fr>
[-- Attachment #1: Type: text/plain, Size: 1612 bytes --]
(On the other hand, the remark that the existing uses of keyword-bang in
the language, namely (method!) and (open!), could now be represented as
annotations is fairly reasonable.)
On Mon, Jan 19, 2015 at 9:34 AM, Alain Frisch <alain@frisch.fr> wrote:
> On 01/19/2015 08:33 AM, oleg@okmij.org wrote:
>
>> Current OCaml syntax has shortage of pattern binding expression and
>>> only usable is let%xxx p = e in which is a bit pain for ppx writers.
>>>
>>
>> Indeed. One may wish that
>>
>> let rec p = e1 in e2
>>
>> were treated as if it were
>> let[@ocaml.let "rec"] p = e1 in e2
>>
>> and likewise let module.
>>
>
> Please, no! Attributes are intended to add meta-data for external tools
> (ppx, tools parsing .cmt files, etc), perhaps also to tweak the behavior of
> the compiler (trigger/control warnings, etc), certainly not to encode core
> language features (otherwise, let's use s-expressions instead of
> Parsetree). Facilitating language experiments is also a good use for
> attributes, but not as a long-term solution for the official compiler.
>
> Come to think of it, 'rec! or 'module' are
>> annotations on let.
>>
>
> "let module" has a different shape (module identifiers/types/expressions)
> than "let". And it doesn't seem realistic to merge, say, core types and
> module types, or core expressions and module expressions.
>
>
> Alain
>
>
> --
> 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: 2816 bytes --]
next prev parent reply other threads:[~2015-01-19 9:07 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 [this message]
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
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='CAPFanBF4n2C8nRn9aDuWRLpnN04xxiTKYYPYmcr-Ar=L_tgVMA@mail.gmail.com' \
--to=gabriel.scherer@gmail.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