unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Arne Babenhauserheide <arne_bab@web.de>
To: Amirouche Boubekki <amirouche@hypermove.net>
Cc: guile-user@gnu.org,
	guile-user <guile-user-bounces+amirouche=hypermove.net@gnu.org>,
	Ian Price <ianprice90@gmail.com>
Subject: Re: Summer of Code Recap
Date: Sat, 02 Sep 2017 08:58:55 +0200	[thread overview]
Message-ID: <87bmmtbn0z.fsf@web.de> (raw)
In-Reply-To: <40d9af53c985dfe680d8df822ace02a3@hypermove.net>

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


Amirouche Boubekki <amirouche@hypermove.net> writes:

> On 2017-08-28 20:56, Ian Price wrote:
> Apparently webkit does ship TCO and safari is the only browser [0] 
> shipping it.
> So it will happen soon enough for chrome, but chrome is not a solution 
> for many
> of us. I don't know when firefox with ship TCO.
>
> [0] https://www.chromestatus.com/feature/5516876633341952

Firefox tracks tail recursion support here:

https://bugzilla.mozilla.org/show_bug.cgi?id=723959

And I just found a JS library which turns functions into tail recursive
ones with 1-4x time overhead:

http://glat.info/pub/tailopt-js/

So it might be possible to check for recursion support and just insert
this as a fallback for browsers which do not support proper tail
recursion (i.e. by implementing it as an identity function in those
which support proper tail recursion).

Best wishes,
Arne
-- 
Unpolitisch sein
heißt politisch sein
ohne es zu merken

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]

  reply	other threads:[~2017-09-02  6:58 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-28 18:56 Summer of Code Recap Ian Price
2017-08-28 19:25 ` Christopher Allan Webber
2017-08-28 19:58   ` Nala Ginrut
2017-08-28 21:39 ` Amirouche
2017-08-29  3:27   ` Christopher Allan Webber
2017-09-01 22:09 ` Amirouche Boubekki
2017-09-02  6:58   ` Arne Babenhauserheide [this message]
2017-09-06 18:25   ` Amirouche Boubekki
2017-09-07  6:32     ` Amirouche Boubekki
2017-09-08 12:18       ` Amirouche Boubekki
2021-05-11 14:45 ` Christopher Lemmer Webber
2021-05-11 15:08   ` Christopher Lemmer Webber
2021-05-11 15:19     ` Christopher Lemmer Webber
2021-10-11  1:50       ` Christine Lemmer-Webber
2021-10-11  5:28         ` Dr. Arne Babenhauserheide
2021-05-11 15:50   ` Dr. Arne Babenhauserheide

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

  List information: https://www.gnu.org/software/guile/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87bmmtbn0z.fsf@web.de \
    --to=arne_bab@web.de \
    --cc=amirouche@hypermove.net \
    --cc=guile-user-bounces+amirouche=hypermove.net@gnu.org \
    --cc=guile-user@gnu.org \
    --cc=ianprice90@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 read-only IMAP folder(s) and NNTP newsgroup(s).