[racket] moby/wescheme & TCO

On Sun, Jan 30, 2011 at 9:04 AM, David Herman <dherman at ccs.neu.edu> wrote:

>
> Since Chrome seems to have gotten away with dropping it to 4ms, we may be
> able to do the same -- though I haven't heard anyone specifically say they
> planned to. Maybe at some point we can eliminate this silliness altogether,
> and setTimeout could become a more viable tool for compiler-writers. But
> happily, the ECMAScript committee recently agreed to try to mandate proper
> tail calls in the next version of the standard. So with a little (okay,
> maybe more than a little) luck, compiler-writers may eventually be able to
> rely on having tail calls built in to the web.
>

Yeah I've heard about that too, but of course it will take sometime for the
change to propagate to all of the browsers in the wild ;)

Thanks for the info,
yc
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.racket-lang.org/users/archive/attachments/20110131/9e4960dc/attachment.html>