From: Stefan Israelsson Tampe <stefan.itampe@gmail.com>
To: guile-devel <guile-devel@gnu.org>
Subject: Fwd: Pausable continuations
Date: Sun, 13 Feb 2022 10:34:57 +0100 [thread overview]
Message-ID: <CAGua6m1M+XBR5L-6CH=4BZAoPECNH_2MzXQwuerPWbwf+aT_Rg@mail.gmail.com> (raw)
In-Reply-To: <CAGua6m24aa+goaczoX-UaDCsGnKEAE6sBfH8Xx-2ks0UjOyvUQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 951 bytes --]
---------- Forwarded message ---------
From: Stefan Israelsson Tampe <stefan.itampe@gmail.com>
Date: Sat, Feb 12, 2022 at 5:04 AM
Subject: Re: Pausable continuations
To: Vijay Marupudi <vijay@vijaymarupudi.com>
I would say that they represent the same idea but that using separate
stacks is an optimization and I intended to explore what to
gain with such a construct and possible variants. The final interface and
implementation will most likely differ, if we decide that
we want this, and be more well designed and integrated. But I intend to put
it in use in different applications and try to take
it to it's limits. Let me know if I shall publish the branch I'm working in
and what's the best way to publish it.
Regards
Stefan
On Fri, Feb 11, 2022 at 7:56 PM Vijay Marupudi <vijay@vijaymarupudi.com>
wrote:
> This is exciting work, thanks for sharing! Maybe non-continuable
> exceptions could be based on pausing continuations.
>
> ~ Vijay
>
[-- Attachment #2: Type: text/html, Size: 1645 bytes --]
next prev parent reply other threads:[~2022-02-13 9:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-10 13:07 Pausable continuations Stefan Israelsson Tampe
2022-02-10 15:19 ` Stefan Israelsson Tampe
2022-02-11 12:06 ` Stefan Israelsson Tampe
2022-02-11 12:10 ` Stefan Israelsson Tampe
2022-02-11 18:56 ` Vijay Marupudi
[not found] ` <CAGua6m24aa+goaczoX-UaDCsGnKEAE6sBfH8Xx-2ks0UjOyvUQ@mail.gmail.com>
2022-02-13 9:34 ` Stefan Israelsson Tampe [this message]
2022-02-13 9:34 ` Stefan Israelsson Tampe
2022-02-13 10:27 ` Mikael Djurfeldt
2022-02-13 10:31 ` Stefan Israelsson Tampe
2022-02-17 6:07 ` Stefan Israelsson Tampe
2022-02-17 16:37 ` Vijay Marupudi
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='CAGua6m1M+XBR5L-6CH=4BZAoPECNH_2MzXQwuerPWbwf+aT_Rg@mail.gmail.com' \
--to=stefan.itampe@gmail.com \
--cc=guile-devel@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).