From: yyoncho <yyoncho@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Zhu Zihao <all_but_last@163.com>,
ak@akirakyle.com, emacs-devel <emacs-devel@gnu.org>
Subject: Re: "Asynchronous Requests from Emacs Dynamic Modules"
Date: Sat, 31 Oct 2020 11:45:35 +0200 [thread overview]
Message-ID: <CACCVLQXnnddWv15Ha24sp9L09FPkoGMPq4+tiPGrrUe-4GddSw@mail.gmail.com> (raw)
In-Reply-To: <83lffmhi5y.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 708 bytes --]
That is unfortunate. I was assuming that at least thread primitives can be
made thread-safe.
On Sat, Oct 31, 2020 at 11:14 AM Eli Zaretskii <eliz@gnu.org> wrote:
> > From: yyoncho <yyoncho@gmail.com>
> > Date: Sat, 31 Oct 2020 10:02:41 +0200
> > Cc: Zhu Zihao <all_but_last@163.com>, ak@akirakyle.com,
> > emacs-devel <emacs-devel@gnu.org>
> >
> > Allowing condition-notify call from non-elisp threads would solve the
> problem as well.
>
> I don't see how that could be possible without redesigning the entire
> Lisp threads machinery.
>
> In general, no part of the Lisp interpreter -- and that includes the
> Lisp thread related functions -- can ever safely run from an async
> non-Lisp thread.
>
[-- Attachment #2: Type: text/html, Size: 1306 bytes --]
next prev parent reply other threads:[~2020-10-31 9:45 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-30 21:35 "Asynchronous Requests from Emacs Dynamic Modules" Akira Kyle
2020-10-30 22:39 ` Stefan Monnier
2020-10-31 3:18 ` Zhu Zihao
2020-10-31 7:45 ` Eli Zaretskii
2020-10-31 8:02 ` yyoncho
2020-10-31 9:13 ` Eli Zaretskii
2020-10-31 9:45 ` yyoncho [this message]
2020-10-31 10:43 ` Eli Zaretskii
2020-10-31 19:25 ` Akira Kyle
2020-10-31 20:18 ` Eli Zaretskii
2020-11-01 0:14 ` Akira Kyle
2020-11-01 18:28 ` Eli Zaretskii
2020-11-01 20:15 ` Akira Kyle
2020-11-01 20:51 ` async-await (was: Re: "Asynchronous Requests from Emacs Dynamic Modules") Philipp Stephani
2020-11-02 15:22 ` "Asynchronous Requests from Emacs Dynamic Modules" Eli Zaretskii
2020-10-31 7:36 ` Philipp Stephani
2020-10-31 12:49 ` Stefan Monnier
2020-11-01 20:18 ` Akira Kyle
2020-11-01 20:32 ` Philipp Stephani
2020-11-20 15:54 ` Zhu Zihao
2020-11-20 16:04 ` Robert Pluim
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=CACCVLQXnnddWv15Ha24sp9L09FPkoGMPq4+tiPGrrUe-4GddSw@mail.gmail.com \
--to=yyoncho@gmail.com \
--cc=ak@akirakyle.com \
--cc=all_but_last@163.com \
--cc=eliz@gnu.org \
--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).