all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "T.V Raman" <raman@google.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Arthur Miller <arthur.miller@live.com>,  emacs-devel@gnu.org
Subject: Re: Experiment with threads - no concurrency?
Date: Mon, 06 Sep 2021 10:38:21 -0700	[thread overview]
Message-ID: <p911r61ioz6.fsf@google.com> (raw)
In-Reply-To: <jwvbl557n47.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Mon, 06 Sep 2021 11:17:00 -0400")

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=gb18030, Size: 804 bytes --]

Stefan Monnier <monnier@iro.umontreal.ca> writes:


Also, see a message I sent a  couple of weeks ago re threading, how
little it is used in emacs itself (from my quick check not at all).

It would be good to have a few exemplars of where emacs' thread support
actually helps to learn from and build out of going forward.
>> Since it is kind of lot's of I/O and independent tasks to do, I thought threads
>> could come handy. However I see no difference from sequential code.
>
> This is a common misunderstanding, it seems.  To help us fix it, could
> you tell us what parts of our docs (docstrings or Texinfo manual) you
> consulted before coming here?
>
>
>         Stefan
>
>

-- 

Thanks,

--Raman(I Search, I Find, I Misplace, I Research)
7©4 Id: kg:/m/0285kf1  •0Ü8



  parent reply	other threads:[~2021-09-06 17:38 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-06 14:35 Experiment with threads - no concurrency? Arthur Miller
2021-09-06 15:17 ` Stefan Monnier
2021-09-06 16:35   ` Arthur Miller
2021-09-06 17:31     ` Eli Zaretskii
2021-09-06 17:38   ` T.V Raman [this message]
2021-09-06 18:11     ` Arthur Miller
2021-09-06 15:47 ` Eli Zaretskii
2021-09-06 16:40   ` Arthur Miller
2021-09-06 17:33     ` Eli Zaretskii
2021-09-06 18:10       ` Arthur Miller

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=p911r61ioz6.fsf@google.com \
    --to=raman@google.com \
    --cc=arthur.miller@live.com \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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.