caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: ivan chollet <ivan.chollet@gmail.com>
To: Jonathan Protzenko <jonathan.protzenko@gmail.com>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Custom let bindings
Date: Sun, 22 Jan 2012 12:18:00 +0000	[thread overview]
Message-ID: <CACm_MF851VtvqG7Z_Wb-jkoy78fWaS8qgeV2h9o=CCyjA+6_JA@mail.gmail.com> (raw)
In-Reply-To: <4F1BE848.5050200@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2438 bytes --]

pretty enough.
In general, I think these read-only discussions from the caml-devel mailing
list are of great educational value for students and ocaml users, and would
deserve their very own public archive like what has been done for the
general caml mailing list.


On Sun, Jan 22, 2012 at 10:43 AM, Jonathan Protzenko <
jonathan.protzenko@gmail.com> wrote:

> Hi folks,
>
> I've put a raw, not pretty dump of the discussion at <
> http://pauillac.inria.fr/~**protzenk/let-bang.html<http://pauillac.inria.fr/%7Eprotzenk/let-bang.html>>.
> We didn't reach any consensus there, and we've covered the subject
> extensively. I'm just publishing it if anyone's interested.
>
> Please refrain from adding any extra messages to this thread, unless you
> have arguments that make one proposal *clearly, objectively better than the
> others*. There's been enough back-and-forth already, so any arguments such
> as "/me likes" or "just pick any one of them" will be happily dismissed.
>
> Thanks,
>
> jonathan
>
>
> On Sun 22 Jan 2012 11:23:45 AM CET, Xavier Leroy wrote:
>
>> On 01/20/2012 01:39 PM, Mehdi Dogguy wrote:
>>
>>  I noticed that Alain Frisch tried to add custom let bindings (see r11894
>>> and r11906) but it was reverted later on (see r11960) because no
>>> consensus was reached (among OCaml Core team, I guess).
>>>
>>
>> Yes.  We Caml developers spent a lot of time arguing about the merits and
>> demerits of various syntaxes for monadic lets and other forms of
>> generalized let bindings, discussing usability, generality, etc.
>> There were some unexpected surprises, e.g. Lwt's concurrency monad
>> needing a special monadic "let ... and ... in ..."  binding, which
>> makes sense for this particular monad but not for others.
>>
>> In the end, we decided that none of the proposals is something we can
>> commit on and put (forever) in the core language.  This is one of the
>> cases that is currently best handled by Camlp4 syntax extensions,
>> either specific to a monad (Lwt) or more general (pa_monad).
>>
>> Regards,
>>
>> - Xavier Leroy
>>
>>
> --
> Caml-list mailing list.  Subscription management and archives:
> https://sympa-roc.inria.fr/**wws/info/caml-list<https://sympa-roc.inria.fr/wws/info/caml-list>
> Beginner's list: http://groups.yahoo.com/group/**ocaml_beginners<http://groups.yahoo.com/group/ocaml_beginners>
> Bug reports: http://caml.inria.fr/bin/caml-**bugs<http://caml.inria.fr/bin/caml-bugs>
>
>

[-- Attachment #2: Type: text/html, Size: 3265 bytes --]

  reply	other threads:[~2012-01-22 12:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-20 12:39 Mehdi Dogguy
2012-01-20 12:47 ` Yaron Minsky
2012-01-22 10:23 ` Xavier Leroy
2012-01-22 10:43   ` Jonathan Protzenko
2012-01-22 12:18     ` ivan chollet [this message]
2012-01-22 15:18   ` Jacques Carette

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='CACm_MF851VtvqG7Z_Wb-jkoy78fWaS8qgeV2h9o=CCyjA+6_JA@mail.gmail.com' \
    --to=ivan.chollet@gmail.com \
    --cc=caml-list@inria.fr \
    --cc=jonathan.protzenko@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;
as well as URLs for NNTP newsgroup(s).