unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Christopher Lemmer Webber <cwebber@dustycloud.org>
To: John Wiegley <johnw@gnu.org>
Cc: Michael Heerdegen <michael_heerdegen@web.de>,
	Stefan Monnier <monnier@iro.umontreal.ca>,
	emacs-devel@gnu.org
Subject: Re: Delimited continuations
Date: Tue, 02 Jan 2018 12:39:51 -0600	[thread overview]
Message-ID: <87efn8yuiw.fsf@dustycloud.org> (raw)
In-Reply-To: <m27etrlh45.fsf@newartisans.com>

John Wiegley writes:

>>>>>> "MH" == Michael Heerdegen <michael_heerdegen@web.de> writes:
>
> HM> Or we just don't call it continuation, which is misleading given the
> MH> suggested implementation which gives you more something like a delimited
> MH> re-execution.

The term "prompts" are often also used for delimited continuations in
Scheme-land at least: https://www.gnu.org/software/guile/manual/html_node/Prompts.html

(But they are continuations... they're delimited rather than
undelimited... that's a big advantage though because delimited
continuations compose)

> HM> Anyway, my personal opinion is to make such stuff available so that people
> HM> can experiment with it.
>
> I'll create some examples in Haskell to determine what the intended semantics
> should be, and then see how to efficiently replicate that behavior in Elisp.

May be even easier to show how delimited continuations work in schemes
like Guile or Racket, since that looks a bit more native.  In Scheme
examples you also don't need to manually do the CPS conversion... it's
done for you.

But I guess that leads to something I was unclear on: John, are you
suggesting that we make delimited continuations part of the language
(with automatic CPS conversion)?  If that's possible, it would be a big
win.  But maybe you were just demo'ing how to do delimited continuations
manually?

IMO manual CPS is cool to know how to do, but it's much nicer if your
language can do it for you :)

Go go delimited continuations!
 - Chris




  reply	other threads:[~2018-01-02 18:39 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 [this message]
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   ` Real continuations Stefan Monnier

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=87efn8yuiw.fsf@dustycloud.org \
    --to=cwebber@dustycloud.org \
    --cc=emacs-devel@gnu.org \
    --cc=johnw@gnu.org \
    --cc=michael_heerdegen@web.de \
    --cc=monnier@iro.umontreal.ca \
    /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).