From: chad <yandros@mit.edu>
To: emacs-tangents@gnu.org, arthur.miller@live.com
Cc: Konstantin Kharlamov <Hi-Angel@yandex.ru>
Subject: Re: Info: No GIL Multithreading strat for Python
Date: Mon, 4 Mar 2024 19:44:58 -0500 [thread overview]
Message-ID: <CAO2hHWYuNj8LO=vY+BtD1-cqE10A0C=kAXnKdAvzn1mBXmM-TQ@mail.gmail.com> (raw)
In-Reply-To: <86a5nelz4h.fsf@gnu.org>
[-- Attachment #1.1: Type: text/plain, Size: 362 bytes --]
People who are interested in this topic might want to take a look at this
examination of the subject from a couple years back:
https://coredumped.dev/2022/05/19/a-vision-of-a-multi-threaded-emacs/
I suggest follow-ups to emacs-tangents, and have attempted to encourage
that. Please forgive me if my somewhat clumsy attempt to do so goes awry.
Thanks!
~Chad
[-- Attachment #1.2: Type: text/html, Size: 519 bytes --]
[-- Attachment #2: Type: text/plain, Size: 92 bytes --]
---
via emacs-tangents mailing list (https://lists.gnu.org/mailman/listinfo/emacs-tangents)
parent reply other threads:[~2024-03-05 0:44 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <86a5nelz4h.fsf@gnu.org>]
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='CAO2hHWYuNj8LO=vY+BtD1-cqE10A0C=kAXnKdAvzn1mBXmM-TQ@mail.gmail.com' \
--to=yandros@mit.edu \
--cc=Hi-Angel@yandex.ru \
--cc=arthur.miller@live.com \
--cc=emacs-tangents@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.
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).