all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Po Lu <luangruo@yahoo.com>
To: Jim Porter <jporterbugs@gmail.com>
Cc: Stefan Monnier <monnier@iro.umontreal.ca>,
	 Lynn Winebarger <owinebar@gmail.com>,
	 Tomas Hlavaty <tom@logand.com>,
	 Karthik Chikmagalur <karthikchikmagalur@gmail.com>,
	 Thomas Koch <thomas@koch.ro>,
	"emacs-devel@gnu.org" <emacs-devel@gnu.org>
Subject: Re: continuation passing in Emacs vs. JUST-THIS-ONE
Date: Tue, 18 Apr 2023 17:52:33 +0800	[thread overview]
Message-ID: <s8h354x4ivy.fsf@yahoo.com> (raw)
In-Reply-To: <e9ce157e-8fba-5bf3-1591-61a6d5c2d0f2@gmail.com> (Jim Porter's message of "Mon, 17 Apr 2023 23:19:38 -0700")

Jim Porter <jporterbugs@gmail.com> writes:

> On 4/17/2023 12:50 PM, Stefan Monnier wrote:
>>> This whole thread seems to echo the difference between "stackless"
>>> and
>>> "stackful" coroutines discussed in
>>> https://nullprogram.com/blog/2019/03/10/ by the author of
>>> emacs-aio,
>>> with generator-style rewriting corresponding to stackless and
>>> threads
>>> to "stackful".  So when you say "save as much as threads do", I'm
>>> not
>>> clear if you're talking about rewriting code to essentially create
>>> a
>>> heap allocated version of the same information that a thread has in
>>> the form of its stack, or something more limited like some
>>> particular
>>> set of special bindings.
>> Indeed to "save as much as threads do" we'd have to essentially
>> create
>> a heap allocated version of the same info.
>> [ I don't think that's what we want.  ]
>
> I think this subthread is about two different aspects, which is
> probably due in part to me not distinguishing the two enough
> initially; one of the reasons I'd find it useful to "save as much as
> threads do" is so that there could be a path towards packaging tasks
> up to run on another thread, and for them to eventually have enough
> context that we could run multiple packaged tasks
> *concurrently*. That's separate from a more-general asynchronous
> programming library (though they would likely interact with one
> another).
>
> Javascript might be a useful analogue here, since it too was
> originally single-threaded with an event loop, and more concurrency
> features were added in later. Similarly to "modern" JS, we could have
> async/await constructs that (primarily) work on the main thread, plus
> something similar to web workers, which operate as mostly-independent
> threads that you can communicate with via messages.

Btw, even though I don't know exactly what this is about, ISTM that
whatever you're doing could use a name that isn't missing a letter, like
`future'.  Why `futur'?



  reply	other threads:[~2023-04-18  9:52 UTC|newest]

Thread overview: 53+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-11 12:53 continuation passing in Emacs vs. JUST-THIS-ONE Thomas Koch
2023-03-12  1:45 ` Jim Porter
2023-03-12  6:33   ` tomas
2023-03-14  6:39   ` Karthik Chikmagalur
2023-03-14 18:58     ` Jim Porter
2023-03-15 17:48       ` Stefan Monnier
2023-03-17  0:17         ` Tomas Hlavaty
2023-03-17  3:08           ` Stefan Monnier
2023-03-17  5:37             ` Jim Porter
2023-03-25 18:42             ` Tomas Hlavaty
2023-03-26 19:35               ` Tomas Hlavaty
2023-03-28  7:23                 ` Tomas Hlavaty
2023-03-29 19:00                 ` Stefan Monnier
2023-04-03  0:39                   ` Tomas Hlavaty
2023-04-03  1:44                     ` Emanuel Berg
2023-04-03  2:09                     ` Stefan Monnier
2023-04-03  4:03                       ` Po Lu
2023-04-03  4:51                         ` Jim Porter
2023-04-10 21:47                       ` Tomas Hlavaty
2023-04-11  2:53                         ` Stefan Monnier
2023-04-11 19:59                           ` Tomas Hlavaty
2023-04-11 20:22                             ` Stefan Monnier
2023-04-11 23:07                               ` Tomas Hlavaty
2023-04-12  6:13                                 ` Eli Zaretskii
2023-04-17 20:51                                   ` Tomas Hlavaty
2023-04-18  2:25                                     ` Eli Zaretskii
2023-04-18  5:01                                       ` Tomas Hlavaty
2023-04-18 10:35                                       ` Konstantin Kharlamov
2023-04-18 15:31                                         ` [External] : " Drew Adams
2023-03-29 18:47               ` Stefan Monnier
2023-04-17  3:46                 ` Lynn Winebarger
2023-04-17 19:50                   ` Stefan Monnier
2023-04-18  2:56                     ` Lynn Winebarger
2023-04-18  3:48                       ` Stefan Monnier
2023-04-22  2:48                         ` Lynn Winebarger
2023-04-18  6:19                     ` Jim Porter
2023-04-18  9:52                       ` Po Lu [this message]
2023-04-18 12:38                         ` Lynn Winebarger
2023-04-18 13:14                         ` Stefan Monnier
2023-04-19  0:28                           ` Basil L. Contovounesios
2023-04-19  2:59                             ` Stefan Monnier
2023-04-19 13:25                               ` [External] : " Drew Adams
2023-04-19 13:34                                 ` Robert Pluim
2023-04-19 14:19                                   ` Stefan Monnier
2023-04-21  1:33                                     ` Richard Stallman
2023-04-19  1:11                           ` Po Lu
2023-04-17 21:00                   ` Tomas Hlavaty
2023-03-14  3:58 ` Richard Stallman
2023-03-14  6:28   ` Jim Porter
2023-03-16 21:35 ` miha
2023-03-16 22:14   ` Jim Porter
2023-03-25 21:05 ` Tomas Hlavaty
2023-03-26 23:50 ` Tomas Hlavaty

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=s8h354x4ivy.fsf@yahoo.com \
    --to=luangruo@yahoo.com \
    --cc=emacs-devel@gnu.org \
    --cc=jporterbugs@gmail.com \
    --cc=karthikchikmagalur@gmail.com \
    --cc=monnier@iro.umontreal.ca \
    --cc=owinebar@gmail.com \
    --cc=thomas@koch.ro \
    --cc=tom@logand.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.
Code repositories for project(s) associated with this external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.