unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: emacs-devel@gnu.org
Subject: Re: Real continuations
Date: Mon, 11 Dec 2017 11:16:06 -0500	[thread overview]
Message-ID: <jwvk1xtnt7b.fsf-monnier+gmane.emacs.devel@gnu.org> (raw)
In-Reply-To: 877etucwjh.fsf@web.de

> btw, would it be practical to support real first class continuations in
> Elisp?

Real first-class continuations require reifying the stack as an object
reachable from the heap and that can be copied.  There are many
different ways to do that to try and keep the benefits of the normal
representation of the stack, but I think it could prove difficult to
implement something like call/cc given the current code base.

> When you exit a recursive edit, isn't what you get (internally) more or
> less already the execution of some kind of continuation?

Indeed catch/throw do provide some of the functionality of call/cc, as
do threads.  Together they cover a large part of what call/cc is
typically used for, but they still don't provide call/cc.


        Stefan




      reply	other threads:[~2017-12-11 16:16 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-09  9:06 Delimited continuations John Wiegley
2017-12-10 16:53 ` Michael Heerdegen
2017-12-10 19:59   ` John Wiegley
2017-12-12 14:27     ` Michael Heerdegen
2017-12-11 16:47   ` Stefan Monnier
2017-12-12 14:17     ` Michael Heerdegen
2017-12-12 22:24       ` John Wiegley
2018-01-02 18:39         ` Christopher Lemmer Webber
2018-01-02 22:29           ` John Wiegley
2018-01-03 16:01           ` Michael Heerdegen
2018-01-03 20:12             ` Stefan Monnier
2017-12-10 17:39 ` Real continuations (was: Delimited continuations) Michael Heerdegen
2017-12-11 16:16   ` Stefan Monnier [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/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=jwvk1xtnt7b.fsf-monnier+gmane.emacs.devel@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=emacs-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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).