From: Eli Zaretskii <eliz@gnu.org>
To: Tomas Hlavaty <tom@logand.com>
Cc: monnier@iro.umontreal.ca, jporterbugs@gmail.com,
karthikchikmagalur@gmail.com, emacs-devel@gnu.org
Subject: Re: continuation passing in Emacs vs. JUST-THIS-ONE
Date: Wed, 12 Apr 2023 09:13:02 +0300 [thread overview]
Message-ID: <83jzyh8w7l.fsf@gnu.org> (raw)
In-Reply-To: <87v8i2dnm3.fsf@logand.com> (message from Tomas Hlavaty on Wed, 12 Apr 2023 01:07:32 +0200)
> From: Tomas Hlavaty <tom@logand.com>
> Cc: Jim Porter <jporterbugs@gmail.com>,
> Karthik Chikmagalur <karthikchikmagalur@gmail.com>,
> "emacs-devel@gnu.org" <emacs-devel@gnu.org>
> Date: Wed, 12 Apr 2023 01:07:32 +0200
>
> Strange that futur.el is "primarily concerned with making it easier to
> write asynchronous code" but limits itself to asynchronous processes
> only.
Async subprocesses are currently the only feature in Emacs that
provides an opportunity for writing asynchronous code.
> I do not know how useable threads in Emacs are at the moment,
> but they are already there and the examples I tried worked well.
If you think Lisp threads in Emacs allow asynchronous processing, you
are mistaken: they don't. Only one such thread can be running at any
given time. Whereas with async subprocesses, several such
subprocesses could be running at the same time each one doing its own
job (provided that your CPU has more than a single execution unit).
next prev parent reply other threads:[~2023-04-12 6:13 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 [this message]
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
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
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=83jzyh8w7l.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=jporterbugs@gmail.com \
--cc=karthikchikmagalur@gmail.com \
--cc=monnier@iro.umontreal.ca \
--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 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).