From: Arvydas Silanskas <nma.arvydas.silanskas@gmail.com>
To: Duncan Mak <duncanmak@gmail.com>
Cc: Per Bothner <per@bothner.com>, kawa@sourceware.org
Subject: Re: First-class continuations in Kawa
Date: Fri, 9 Dec 2022 12:53:40 +0200 [thread overview]
Message-ID: <CAPh7weD-C5prLo_k78ZQ5zFFGuUutwyhNqr9AKcbWBrcHt7Q0w@mail.gmail.com> (raw)
In-Reply-To: <CABgWrqqRnvjPXj_ZAuPO2LZWAfm8WKtqKo120LRJ8vrbCPZWRQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1379 bytes --]
Continuations are indeed interesting, but hard to implement unfortunately.
As a recap of my merging attempts; base call/cc worked, but I got stuck at
figuring how to get dynamic-wind and other extent-aware features working,
and unfortunately had to stash it
2022-12-08, kt, 01:43 Duncan Mak via Kawa <kawa@sourceware.org> rašė:
> There's a new SRFI effort on refining the continuation API:
>
> SRFI 226: Control Features (schemers.org)
> <https://srfi.schemers.org/srfi-226/srfi-226.html>
>
> It'd be interesting to look into implementing this SRFI for Kawa Scheme.
>
> On Mon, Aug 9, 2021 at 3:42 PM Per Bothner <per@bothner.com> wrote:
>
> > A suggestion: Polish and check in the code in the calcc branch.
> > Then change the interface so it is compatible that the tail-call API.
> > Specifically change the generated "fragments" so each looks like:
> >
> > static Object stubNN(Procedure proc, CallContext ctx) throws
> Throwable)
> > { ... }
> >
> > and call each fragment using MethodHandle#invokeExact.
> >
> > Of course this is not trivial: The person(s) doing this have to
> understand
> > not just logic of callcc changes but also how applyToConsumerMethod and
> > CallContext etc work, before they can synthesize them.
> > --
> > --Per Bothner
> > per@bothner.com http://per.bothner.com/
> >
>
>
> --
> Duncan.
>
prev parent reply other threads:[~2022-12-09 10:53 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-20 0:49 Duncan Mak
2018-01-20 6:47 ` Per Bothner
2018-01-20 16:07 ` Duncan Mak
2018-01-20 23:20 ` Andrea Bernardini
2018-02-21 0:21 ` Andrea Bernardini
2018-02-22 0:38 ` Duncan Mak
2021-05-01 16:15 ` Duncan Mak
2021-05-01 18:45 ` Arvydas Silanskas
2021-05-01 19:06 ` Sudarshan S Chawathe
2021-05-01 20:38 ` Per Bothner
2021-06-09 9:04 ` Arvydas Silanskas
2021-06-09 23:27 ` Per Bothner
2021-08-08 14:29 ` Arvydas Silanskas
2021-08-08 15:53 ` Andrea Bernardini
2021-08-08 23:52 ` Per Bothner
2021-08-09 19:41 ` Per Bothner
2022-12-07 23:42 ` Duncan Mak
2022-12-09 10:53 ` Arvydas Silanskas [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAPh7weD-C5prLo_k78ZQ5zFFGuUutwyhNqr9AKcbWBrcHt7Q0w@mail.gmail.com \
--to=nma.arvydas.silanskas@gmail.com \
--cc=duncanmak@gmail.com \
--cc=kawa@sourceware.org \
--cc=per@bothner.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).