From: Zelphir Kaltstahl <zelphirkaltstahl@posteo.de>
To: Christine Lemmer-Webber <cwebber@dustycloud.org>
Cc: Guile User <guile-user@gnu.org>
Subject: Re: Directly compiling Scheme to WebAssembly: lambdas, recursion, iteration!
Date: Wed, 31 May 2023 07:51:22 +0000 [thread overview]
Message-ID: <13fbfea5-c59a-e1f2-12dc-1fab8e3f420c@posteo.de> (raw)
In-Reply-To: <87h6rtzohw.fsf@dustycloud.org>
On 5/30/23 19:59, Christine Lemmer-Webber wrote:
> The Hoot team (meaning really Andy Wingo and Robin Templeton) have been
> hard at work bringing that dream to life. We don't have full r7rs-small
> scheme *yet* but... we're on our way! :)
>
> Here's an update!
>
> https://spritely.institute/news/scheme-to-wasm-lambdas-recursion.html
>
> And yes, there's real code! It does require a development version of
> Guile though... Guix makes this easy to run though, thankfully:
>
> https://gitlab.com/spritely/guile-hoot/
>
> Well, "make check" is easy to run, I should say. We're not at the point
> where you can pick up and use this for your projects yet. But that's
> the goal obviously... and we're on our way!
>
> Happy hacking!
> - Christine Lemmer-Webber, the Spritely Institute, and the Hoot team
>
Thank you people @ spritely and elsewhere for moving Guile ahead!
This one may be the one making me look into WASM at some point and thus being
yet another case, where Guile is my learning vehicle and means of exploration,
that it has been so often already. Maybe some day I will also know more stuff
about compilers and will be able to understand how to make such a thing :D
It seems to me many great things have been done recently.
Best wishes,
Zelphir
--
repositories: https://notabug.org/ZelphirKaltstahl
prev parent reply other threads:[~2023-05-31 7:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-30 17:59 Directly compiling Scheme to WebAssembly: lambdas, recursion, iteration! Christine Lemmer-Webber
2023-05-31 6:14 ` Jérémy Korwin-Zmijowski.fr
2023-05-31 7:51 ` Zelphir Kaltstahl [this message]
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=13fbfea5-c59a-e1f2-12dc-1fab8e3f420c@posteo.de \
--to=zelphirkaltstahl@posteo.de \
--cc=cwebber@dustycloud.org \
--cc=guile-user@gnu.org \
/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).