From: Christopher Allan Webber <cwebber@dustycloud.org>
To: Andy Wingo <wingo@pobox.com>
Cc: guile-devel@gnu.org
Subject: Re: guile 3 update
Date: Mon, 30 Oct 2017 14:31:36 -0500 [thread overview]
Message-ID: <87zi88qvon.fsf@dustycloud.org> (raw)
In-Reply-To: <874lqgoh6v.fsf@pobox.com>
Andy Wingo writes:
> Hi :)
>
> On Sun 22 Oct 2017 15:22, Christopher Allan Webber <cwebber@dustycloud.org> writes:
>
>> - Could native code compilation also be a step towards WASM, assuming
>> they lend us their GC?
>
> Regarding this question: yes! Specifically with the "GC" proposal
> (which in reality is much more:
> https://github.com/WebAssembly/gc/blob/master/proposals/gc/Overview.md)
> I think that we will approach WASM's semantic level. There are some
> open questions of course, like how to deal with the stack and delimited
> continuations, how to do bignums with overflow, etc; but yeah we're
> getting there.
>
> Andy
This is very exciting!
prev parent reply other threads:[~2017-10-30 19:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-22 10:24 guile 3 update Andy Wingo
2017-10-22 13:22 ` Christopher Allan Webber
2017-10-30 14:15 ` Andy Wingo
2017-10-30 19:31 ` Christopher Allan Webber [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=87zi88qvon.fsf@dustycloud.org \
--to=cwebber@dustycloud.org \
--cc=guile-devel@gnu.org \
--cc=wingo@pobox.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).