From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: noverlay branch Date: Fri, 07 Oct 2022 09:33:47 -0400 Message-ID: References: <1468ca31-1703-82a1-0c8c-be2c5b5674a7@gmail.com> <87r0zld0de.fsf@rfc20.org> <87edvki88a.fsf@rfc20.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="15624"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/29.0.50 (gnu/linux) Cc: Matt Armstrong , emacs-devel@gnu.org To: Gerd =?windows-1252?Q?M=F6llmann?= Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Fri Oct 07 16:56:53 2022 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 1ogomT-0003sT-1N for ged-emacs-devel@m.gmane-mx.org; Fri, 07 Oct 2022 16:56:53 +0200 Original-Received: from localhost ([::1]:38578 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1ogomS-0001eU-1F for ged-emacs-devel@m.gmane-mx.org; Fri, 07 Oct 2022 10:56:52 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:43570) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1ognUL-0002bm-Oa for emacs-devel@gnu.org; Fri, 07 Oct 2022 09:34:08 -0400 Original-Received: from mailscanner.iro.umontreal.ca ([132.204.25.50]:16730) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1ognUI-00058L-2F for emacs-devel@gnu.org; Fri, 07 Oct 2022 09:34:03 -0400 Original-Received: from pmg1.iro.umontreal.ca (localhost.localdomain [127.0.0.1]) by pmg1.iro.umontreal.ca (Proxmox) with ESMTP id 6CDA1100142; Fri, 7 Oct 2022 09:33:58 -0400 (EDT) Original-Received: from mail01.iro.umontreal.ca (unknown [172.31.2.1]) by pmg1.iro.umontreal.ca (Proxmox) with ESMTP id E84271000E7; Fri, 7 Oct 2022 09:33:56 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=iro.umontreal.ca; s=mail; t=1665149636; bh=OgRZfBm7D5MzefxDt2I5/O1bQ5lC3iseKj/G5m/regA=; h=From:To:Cc:Subject:In-Reply-To:References:Date:From; b=AhBCun7/Msx6nmTwomtCO+F/cLSs1o32WKr2N9nvK02etBiP5WSmHnr4NcYpWvTI2 07I1IC57FspFwT4eHwGI+uxfQ7oJLq5vRG36WpvR+zOgD7zBDf/D5Kq5nZMPckC/JJ c4b6sSm0/QCAk2f2c8j463qHZpDUHa7RLAI39P7QsVM+12UKixeVVHu0ArK+qiYa2T ibFJSF1qoBQ/GXdtmaun24l7skaxA7Za6BIDygEPN5VNwHpkQuBqama8N+a5w8yI44 fOG6rfhb3GWVRNQKnEo549N1lQXW2IItEtwEhDbdsjkZRch2ZuEIXobTxLeMW6HiMX wnekrTmxzLZpg== Original-Received: from pastel (65-110-220-202.cpe.pppoe.ca [65.110.220.202]) by mail01.iro.umontreal.ca (Postfix) with ESMTPSA id 9D89B1208CE; Fri, 7 Oct 2022 09:33:56 -0400 (EDT) In-Reply-To: ("Gerd =?windows-1252?Q?M=F6l?= =?windows-1252?Q?lmann=22's?= message of "Fri, 07 Oct 2022 06:34:31 +0200") Received-SPF: pass client-ip=132.204.25.50; envelope-from=monnier@iro.umontreal.ca; helo=mailscanner.iro.umontreal.ca X-Spam_score_int: -42 X-Spam_score: -4.3 X-Spam_bar: ---- X-Spam_report: (-4.3 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=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" Xref: news.gmane.io gmane.emacs.devel:297154 Archived-At: > to allow C++. With std::multimap/std::multiset, we would have a > ready-made complete solution for the tree, tested by a gazillion of > users. Just dreaming :-)) I'm not familiar with C++ libs: does this `multiset` lib offer something similar to the lazy update of buffer positions that Andreas's code uses (via the `offset` field together with the `interval_tree_inherit_offset` function)? >> I think in the context of this overlay work the performance difference >> is not very significant, since the code is doing a lot of other stuff >> while traversing the tree. > I agree. I think NULL could be better in multi-threaded cases, as > Stefan alluded to. The current code should be multi-thread safe (except for the global iterator, of course), despite its use of a global sentinel node: there's no need to synchronize anything when reading a read-only field or when writing a write-only field. Stefan