From: Grant Rettke <grettke@acm.org>
To: Ashish Agarwal <agarwal1975@gmail.com>
Cc: Stefan Monnier <monnier@iro.umontreal.ca>, caml-list@inria.fr
Subject: WAS Re: [Caml-list] Re: The need to specify 'rec' in a recursive function defintion
Date: Tue, 16 Feb 2010 10:47:03 -0600 [thread overview]
Message-ID: <756daca51002160847k1a416f01p36cc192d00e25697@mail.gmail.com> (raw)
On Tue, Feb 16, 2010 at 10:21 AM, Ashish Agarwal <agarwal1975@gmail.com> wrote:
> let rec
Do OCaml'er look at let rec more as being a message to the programmer,
rather than the compiler, that the way I want to define this function
is recursively so even if 'f' was previously bound you know which one
I mean?
Considering the language allows mutation, I feel like it is more for
humans than the compiler, but of course, the compiler must be told,
too.
next reply other threads:[~2010-02-16 16:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-16 16:47 Grant Rettke [this message]
2010-02-16 18:08 ` Jon Harrop
2010-02-17 17:09 ` Andrej Bauer
2010-05-29 21:27 ` Grant Rettke
2010-05-29 21:27 ` Grant Rettke
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=756daca51002160847k1a416f01p36cc192d00e25697@mail.gmail.com \
--to=grettke@acm.org \
--cc=agarwal1975@gmail.com \
--cc=caml-list@inria.fr \
--cc=monnier@iro.umontreal.ca \
/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).