From: Yitzhak Mandelbaum <yitzhakm@CS.Princeton.EDU>
To: Jerome Vouillon <Jerome.Vouillon@pps.jussieu.fr>
Cc: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] [ANN] Js_of_ocaml version 1.0
Date: Mon, 13 Dec 2010 09:58:27 -0500 [thread overview]
Message-ID: <0C2C6562-3389-4B61-B0E2-69EF3EAB1418@cs.princeton.edu> (raw)
In-Reply-To: <20101213130645.GA27585@pps.jussieu.fr>
Jerome,
Thank you, this sounds fantastic!
One small question: could you expand on your last comment:
On Dec 13, 2010, at 8:06 AM, Jerome Vouillon wrote:
> <snip>
>
> Ocamljs optimizes tail recursion, but this comes at a large
> performance cost.
Do you mean all tail-calls come a large cost, or only those outside of plain tail-recursion? Either way, could you give us some more intuition as to why this happens, and why js_of_ocaml doesn't suffer from the same problem (assuming it applies to tail-recursion)?
Thanks,
Yitzhak
-----------------------------
Yitzhak Mandelbaum
next prev parent reply other threads:[~2010-12-13 14:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-13 13:06 Jerome Vouillon
2010-12-13 14:58 ` Yitzhak Mandelbaum [this message]
2010-12-13 15:45 ` [Caml-list] " Jerome Vouillon
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=0C2C6562-3389-4B61-B0E2-69EF3EAB1418@cs.princeton.edu \
--to=yitzhakm@cs.princeton.edu \
--cc=Jerome.Vouillon@pps.jussieu.fr \
--cc=caml-list@yquem.inria.fr \
/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).