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 10:51:25 -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="32324"; 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 18:10:01 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 1ogpvE-0008B6-T6 for ged-emacs-devel@m.gmane-mx.org; Fri, 07 Oct 2022 18:10:01 +0200 Original-Received: from localhost ([::1]:54810 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1ogpvD-0005IK-NC for ged-emacs-devel@m.gmane-mx.org; Fri, 07 Oct 2022 12:09:59 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:34622) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1ogohK-000307-Ie for emacs-devel@gnu.org; Fri, 07 Oct 2022 10:51:36 -0400 Original-Received: from mailscanner.iro.umontreal.ca ([132.204.25.50]:13212) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1ogohI-0000sn-7R for emacs-devel@gnu.org; Fri, 07 Oct 2022 10:51:33 -0400 Original-Received: from pmg2.iro.umontreal.ca (localhost.localdomain [127.0.0.1]) by pmg2.iro.umontreal.ca (Proxmox) with ESMTP id C7CA3807AF; Fri, 7 Oct 2022 10:51:29 -0400 (EDT) Original-Received: from mail01.iro.umontreal.ca (unknown [172.31.2.1]) by pmg2.iro.umontreal.ca (Proxmox) with ESMTP id A96E380411; Fri, 7 Oct 2022 10:51:27 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=iro.umontreal.ca; s=mail; t=1665154287; bh=KHZdEjPKKAv4abUUcRom118kUxNsilnNKxaWhNwrwZE=; h=From:To:Cc:Subject:In-Reply-To:References:Date:From; b=aRwqByIa5btamTu1HWOXSCGr6iWNnInaqvpFdAB0PQrz/ZyF7DdOGNRO783RNSjtX EU02d/DzNwixVfVy/DcrSV4DIDhpvYLkJ80KAIKDK67nj1Mo16gjWCNX9fW5tR67j/ TOFSpIooisvKQnNfnwGeJmNqhBtH/CqMkm5Y23Okug3FGog3yXluV7DgWMJXRIOrve zq+rFLKcMlSMDbcZOzqf3rOfnPXCqfRkcQBTePQhUXg+57UnbBuAe4FtdRDZZKMRvt x/PeYBYvkRSGsqI8vjQ/wMF1aky3xVbaNoIE8beHRCaPBaoE67E9wwlD4jSscZMHXs E7wFWSNkmyo6w== Original-Received: from pastel (65-110-220-202.cpe.pppoe.ca [65.110.220.202]) by mail01.iro.umontreal.ca (Postfix) with ESMTPSA id 7C524120E90; Fri, 7 Oct 2022 10:51:27 -0400 (EDT) In-Reply-To: ("Gerd =?windows-1252?Q?M=F6l?= =?windows-1252?Q?lmann=22's?= message of "Fri, 07 Oct 2022 16:29:23 +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:297161 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)? > > No, just the tree-part, or better said not the tree directly. These > implement an abstraction of an ordered set, or multiset (containing an > element more than once), or map of (key, value) pairs, or multimap > (multiple (key, value) pairs with the same key. Then I don't see how it would be a "ready-made complete solution" because it doesn't seem easy to make such updates lazily "from the outside". Stefan