From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Ihor Radchenko Newsgroups: gmane.emacs.devel Subject: Re: Concurrency via isolated process/thread Date: Fri, 07 Jul 2023 20:05:53 +0000 Message-ID: <87351zbi72.fsf@localhost> References: <871qhnr4ty.fsf@localhost> <87ilax71wo.fsf@localhost> <878rbtkz2c.fsf@yahoo.com> <87a5w96x2o.fsf@localhost> <87jzvdjjp4.fsf@yahoo.com> <877crd6w53.fsf@localhost> <877crdjiwn.fsf@yahoo.com> <874jmh6v4s.fsf@localhost> <83y1jtgmbw.fsf@gnu.org> <87zg49xfke.fsf@localhost> <83sfa1gjns.fsf@gnu.org> <87r0plxbep.fsf@localhost> <83ilawhpi6.fsf@gnu.org> <87zg48apwr.fsf@localhost> <83edljg8ub.fsf@gnu.org> <87o7knbxr7.fsf@localhost> <838rbrg4mg.fsf@gnu.org> <87ilavbvdr.fsf@localhost> <834jmffvhy.fsf@gnu.org> <878rbrbmwr.fsf@localhost> <83fs5zecpo.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="10725"; mail-complaints-to="usenet@ciao.gmane.io" Cc: luangruo@yahoo.com, emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Fri Jul 07 22:07:07 2023 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1qHrjO-0002aS-QG for ged-emacs-devel@m.gmane-mx.org; Fri, 07 Jul 2023 22:07:06 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1qHriI-0007mS-8y; Fri, 07 Jul 2023 16:05:58 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1qHriG-0007i6-6w for emacs-devel@gnu.org; Fri, 07 Jul 2023 16:05:56 -0400 Original-Received: from mout02.posteo.de ([185.67.36.66]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1qHriE-0005Vn-A3 for emacs-devel@gnu.org; Fri, 07 Jul 2023 16:05:55 -0400 Original-Received: from submission (posteo.de [185.67.36.169]) by mout02.posteo.de (Postfix) with ESMTPS id C96E9240103 for ; Fri, 7 Jul 2023 22:05:51 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.net; s=2017; t=1688760351; bh=HU9Wwa6zhs1hNvvfKLcxqAlkmAelcCxwY8NhCFqERhM=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version:From; b=l6bwcU39cCoXAhB28FAuNboZCZcuGIcwTf9ccl18M/nZOr18WDZGOt9kF5V9wRIwr kNMuLtL6ZxzKDIrIVejvJOpCKgf9HBgB9bL2xNfJXTwkOyEZTcAnMdQmVe9h8Zd/w3 6oxSV8qGnleLpgpvtTTFaAQ6vu19wut37Ls8lar1XXmna6vkgD6HWFQe9e2v29VsCr /YvBNYPRhnr840kQNEctFzVSib2t+lhU/z51tsgfpNvy4XbnK46Aoy+huyB/ooM9SU MiMn6xbFPaDn2UcbKxhnt0b66D4YiQAzRGmQuQF7+44OaMTuAjHtauKYm/BrXRimcK mBguzviwosH8A== Original-Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4QyPXb2pShz6twJ; Fri, 7 Jul 2023 22:05:51 +0200 (CEST) In-Reply-To: <83fs5zecpo.fsf@gnu.org> Received-SPF: pass client-ip=185.67.36.66; envelope-from=yantar92@posteo.net; helo=mout02.posteo.de X-Spam_score_int: -43 X-Spam_score: -4.4 X-Spam_bar: ---- X-Spam_report: (-4.4 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H5=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.devel:307588 Archived-At: Eli Zaretskii writes: >> But how exactly does, say, relocating buffer text can break things? May >> you provide a pseudo-code example? > > ... If you > consider allowing relocation when the buffer is locked, then some of > the threads will be surprised when they try to resume accessing the > buffer text. Can you please provide an example about "surprised"? Do you mean that buffer->pt will no longer be accurate? Something else? >> Then the question is: can the global state be reduced? > > By what measures? Please suggest something concrete here. By transforming some of the global state variables into thread-local variables. >> May it be acceptable to have a limited concurrency where async threads >> are only allowed to modify a portion of the global state? > > I don't see how one can write a useful Lisp program with such > restrictions. Pure, side-effect-free functions, for example. -- Ihor Radchenko // yantar92, Org mode contributor, Learn more about Org mode at . Support Org development at , or support my work at