From: Jean Abou Samra <jean@abou-samra.fr>
To: Arvydas Silanskas <nma.arvydas.silanskas@gmail.com>, guile-devel@gnu.org
Cc: Maxime Devos <maximedevos@telenet.be>, tomas@tuxteam.de
Subject: Re: Guile VM interpreter in GraalVM Truffle framework
Date: Sat, 24 Dec 2022 14:10:31 +0100 [thread overview]
Message-ID: <e898f64a-c10c-0514-4862-2e08304a1438@abou-samra.fr> (raw)
In-Reply-To: <85eebe72-74f8-25e7-dd1b-ddc2c031638e@gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1059 bytes --]
Le 23/12/2022 à 18:06, Arvydas Silanskas a écrit :
> Good day,
>
> I have aspirations to run scheme on graalvm's truffle framework. And
> on superficial research, it seems implementing a Guile VM bytecode
> interpreter could be easiest path. I just want to inquire, if someone
> already had similar ideas and in secrecy is working or planning to on
> this? If you're familiar with truffle (I'm not), any insights on
> "guile on graal" would also be welcome.
I don't know anything about Truffle, but call/cc and delimited
continuations strike me as feature that could be hard to
implement on such a thing. At least, it seems so from
https://www.graalvm.org/latest/reference-manual/ruby/Compatibility/
On the other hand, upwards-only continuations, aka escape continuations,
which are just a different way to do exceptions, should be doable, so
you could probably ship a version of call/cc where the "cont" value in
(call/cc (lambda (cont) ...)) can only be used inside of the lambda.
Same for prompts.
Best,
Jean
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 236 bytes --]
prev parent reply other threads:[~2022-12-24 13:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-23 17:06 Guile VM interpreter in GraalVM Truffle framework Arvydas Silanskas
2022-12-23 20:51 ` Maxime Devos
2022-12-24 0:42 ` Maxime Devos
2022-12-24 5:48 ` tomas
2022-12-24 13:10 ` Jean Abou Samra [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=e898f64a-c10c-0514-4862-2e08304a1438@abou-samra.fr \
--to=jean@abou-samra.fr \
--cc=guile-devel@gnu.org \
--cc=maximedevos@telenet.be \
--cc=nma.arvydas.silanskas@gmail.com \
--cc=tomas@tuxteam.de \
/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).