From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Dmitry Gutov Newsgroups: gmane.emacs.devel Subject: Re: Emacs design and architecture. How about copy-on-write? Date: Sat, 23 Sep 2023 16:08:23 +0300 Message-ID: References: <87cyyhc7uu.fsf@dataswamp.org> <83ttrsg9nx.fsf@gnu.org> <83h6nrg4eg.fsf@gnu.org> <83v8c7elan.fsf@gnu.org> <877conk5ny.fsf@localhost> <83ttrreeu0.fsf@gnu.org> <87bkdzeas1.fsf@localhost> <83cyyfe5l8.fsf@gnu.org> <87led2o0nb.fsf@localhost> <83ttrqcpfb.fsf@gnu.org> <877comnv4a.fsf@localhost> <83fs3ackrq.fsf@gnu.org> <87ttrp89bx.fsf@localhost> <83led1aqnq.fsf@gnu.org> <87v8c3zun7.fsf@localhost> <83r0mr8w0j.fsf@gnu.org> <87bkduxz3l.fsf@localhost> <83cyya75eb.fsf@gnu.org> <877coh2lmd.fsf@localhost> <83r0mp3zh5.fsf@gnu.org> <55f29d31-947f-4cfc-a90e-36b0592ba12e@gutov.dev> <83lecx3uxt.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="3237"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.13.0 Cc: yantar92@posteo.net, acm@muc.de, incal@dataswamp.org, emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sat Sep 23 15:09:49 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 1qk2OJ-0000du-JB for ged-emacs-devel@m.gmane-mx.org; Sat, 23 Sep 2023 15:09:48 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1qk2NI-0003fU-3P; Sat, 23 Sep 2023 09:08:44 -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 1qk2NF-0003fE-Tq for emacs-devel@gnu.org; Sat, 23 Sep 2023 09:08:41 -0400 Original-Received: from wout3-smtp.messagingengine.com ([64.147.123.19]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1qk2N5-0004t1-IV; Sat, 23 Sep 2023 09:08:41 -0400 Original-Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.west.internal (Postfix) with ESMTP id 48CEB320096D; Sat, 23 Sep 2023 09:08:27 -0400 (EDT) Original-Received: from mailfrontend2 ([10.202.2.163]) by compute4.internal (MEProxy); Sat, 23 Sep 2023 09:08:27 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gutov.dev; h=cc :cc:content-transfer-encoding:content-type:content-type:date :date:from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:sender:subject:subject:to:to; s=fm1; t= 1695474506; x=1695560906; bh=5uTbnEa0x4/gzyC0WXKs/cZ4quuzoE5LC5S n6HgLsNo=; b=PBtzk9RByU/zMA1aLUL/X+kH3m3UQM+e5XQS/QUB2RMyB2Z106r SRYhOYVR5uys1pUPAc+fgmMJ5ZSWfyC+sxbiu1RzTpT37xR/pGNI7UtY7fLx3W3v HAzCReVsksKKGvvPCR05zu3hzNL8FvUD/jWHLY9n6mIRNCtrOh/yVC8wTOiWgLID t70hp1vJvUzrvkxfzSJvOHgQhNPu0ACMJE0eBeE7r/C7xyZfd6Ow+VvLRYKZWEsl l5m1SmzDqj4BIXYzw+O+kYmNIAAmn5e6hdRDDGF/qyntS6+fJmIS0h1qzU71dLU0 1hOuaygPGrJIts/X1n+ggHUmOPNMjwpzNDA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:content-type:date:date:feedback-id:feedback-id :from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:sender:subject:subject:to:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; t= 1695474506; x=1695560906; bh=5uTbnEa0x4/gzyC0WXKs/cZ4quuzoE5LC5S n6HgLsNo=; b=CIrlP/wOGr85JJ8oBWr6hdqO8hUzwD+KhbEHb0IBMstH3+M4PAX TOrc59lh6nwOWAs5DrVR7hCHMLzHyycq620c9haphVz9dUQKurzZ9vOt+wFeKiI6 wZwFFsp0oel2QoCzXOfTjwCSrUvqqKAkmvuCyfg/4bzT7Ud5UrKeDNT+o1IAIMx/ PxdDdWNNMWldAvX3piRKfud7Ra5+2tW/hrMXPkbCVZzjrhoq+kWh3GvQvaRajbHt dwiQbulpPc4+DgrVl/HlMEFB+zxTmy5o54bKlhjZYpgOjfODtQZl5Wv9DZdnCnFG 7CgmhLYeVScKPe0rR7iZHt+wCGAvvAI5wsg== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedviedrudeltddgieduucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepkfffgggfuffvvehfhfgjtgfgsehtjeertddtfeejnecuhfhrohhmpeffmhhi thhrhicuifhuthhovhcuoegumhhithhrhiesghhuthhovhdruggvvheqnecuggftrfgrth htvghrnhepiefgteevheevveffheeltdeukeeiieekueefgedugfefgefhudelgfefveel vdevnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhepug hmihhtrhihsehguhhtohhvrdguvghv X-ME-Proxy: Feedback-ID: i0e71465a:Fastmail Original-Received: by mail.messagingengine.com (Postfix) with ESMTPA; Sat, 23 Sep 2023 09:08:24 -0400 (EDT) Content-Language: en-US In-Reply-To: <83lecx3uxt.fsf@gnu.org> Received-SPF: pass client-ip=64.147.123.19; envelope-from=dmitry@gutov.dev; helo=wout3-smtp.messagingengine.com X-Spam_score_int: -35 X-Spam_score: -3.6 X-Spam_bar: --- X-Spam_report: (-3.6 / 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, NICE_REPLY_A=-1.473, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001 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:311001 Archived-At: On 23/09/2023 16:01, Eli Zaretskii wrote: >> Date: Sat, 23 Sep 2023 15:53:11 +0300 >> Cc:acm@muc.de,incal@dataswamp.org,emacs-devel@gnu.org >> From: Dmitry Gutov >> >> On 23/09/2023 14:23, Eli Zaretskii wrote: >>> As a trivial example, any function that modifies a file-visiting >>> buffer could prompt the user if the file was meanwhile modified on >>> disk. This prompt is completely out of control of any Lisp program >>> which does something that modifies buffer text. How do we handle >>> these cases? their name is a legion. >> Any function that prompts the user is not supposed to be fast. So it >> might as well acquire any number of global locks to do that. > That's not my point. My point is that if we say that changes to adapt > existing code to threads are acceptable, we will have to make those > changes all over our infrastructure, otherwise programs written for > threads will not ready for threads 100%. I agree: functions like yes-or-no-p will have to, internally in their implementation, acquire the "redisplay lock" or whatever it'll be called, and do other things to ensure that they work from non-default threads too. This will likely make them a little slower compared to the single-thread model, but hopefully not to a degree that's humanly noticeable.