From: Jim Porter <jporterbugs@gmail.com>
To: miha@kamnitnik.top, Thomas Koch <thomas@koch.ro>,
"emacs-devel@gnu.org" <emacs-devel@gnu.org>
Subject: Re: continuation passing in Emacs vs. JUST-THIS-ONE
Date: Thu, 16 Mar 2023 15:14:52 -0700 [thread overview]
Message-ID: <26126ff4-6e9c-0d45-d92c-95d3280a45e9@gmail.com> (raw)
In-Reply-To: <87ttyknzuq.fsf@miha-pc>
On 3/16/2023 2:35 PM, miha@kamnitnik.top wrote:
> There's also the issue that using continuation passing (async-io)
> doesn't auto-magically solve the re-entrancy issues.
>
> Consider the following hypothetical command, written using JS-style
> async/await operators:
>
> (async-defun insert-some-parent-dirs ()
> (interactive)
> (insert (await (locate-dominating-file default-directory "go.mod")))
> (insert "\n")
> (insert (await (locate-dominating-file default-directory "go.work"))))
>
> If the user executed such a command multiple times in quick succession,
> the executions could happen in parallel and would trample over each
> other.
>
> For each use of "await", the programmer has to think about the
> possibility of other code running "in-between". This style of
> programming may be harder in Elisp which has a lot of global state in
> form of buffer contents, markers and overlays.
Yeah, this isn't easy to fix on its own. The best I can think of (and
this would take quite a bit of experimentation) would be some way of
declaring async functions as non-reentrant for certain contexts. So your
example would be non-reentrant for a given buffer. Some other functions
might be non-reentrant globally, or for a particular argument to the
function.
With a declaration like that, we could hopefully go a fair way towards
solving the problem by serializing any async calls that are non-reentrant.
I hope to test out Stefan's futur.el (and maybe vanilla generator.el) as
a new iterative evaluation backend for Eshell in the coming months;
hopefully that will help produce some more concrete information about
what the pitfalls are.
next prev parent reply other threads:[~2023-03-16 22:14 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
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 [this message]
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=26126ff4-6e9c-0d45-d92c-95d3280a45e9@gmail.com \
--to=jporterbugs@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=miha@kamnitnik.top \
--cc=thomas@koch.ro \
/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.