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: How to add pseudo vector types Date: Sat, 24 Jul 2021 10:08:58 -0400 Message-ID: References: <83h7gw6pyj.fsf@gnu.org> <45EBF16A-C953-42C7-97D1-3A2BFEF7DD01@gmail.com> <83y2a764oy.fsf@gnu.org> <83v95b60fn.fsf@gnu.org> <00DD5BFE-D14E-449A-9319-E7B725DEBFB3@gmail.com> <83r1fz5xr9.fsf@gnu.org> <1AAB1BCC-362B-4249-B785-4E0530E15C60@gmail.com> <83czri67h0.fsf@gnu.org> <46BBFF88-76C3-4818-8805-5437409BEA93@gmail.com> <83wnpq46uk.fsf@gnu.org> <533BD53B-4E85-4E9E-B46A-346A5BBAD0F5@gmail.com> <258CB68D-1CC1-42C8-BDCD-2A8A8099B783@gmail.com> <1a776770-50b7-93cd-6591-c9a5b3a56eb8@gmail.com> <831r7w4yhb.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="6462"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux) Cc: cpitclaudel@gmail.com, emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sat Jul 24 16:09:56 2021 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 1m7ILj-0001Vj-L1 for ged-emacs-devel@m.gmane-mx.org; Sat, 24 Jul 2021 16:09:55 +0200 Original-Received: from localhost ([::1]:44982 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1m7ILi-0005QU-Nf for ged-emacs-devel@m.gmane-mx.org; Sat, 24 Jul 2021 10:09:54 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:39784) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1m7IL9-0004iK-Kw for emacs-devel@gnu.org; Sat, 24 Jul 2021 10:09:19 -0400 Original-Received: from mailscanner.iro.umontreal.ca ([132.204.25.50]:59432) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1m7IL6-0001u3-IM; Sat, 24 Jul 2021 10:09:18 -0400 Original-Received: from pmg3.iro.umontreal.ca (localhost [127.0.0.1]) by pmg3.iro.umontreal.ca (Proxmox) with ESMTP id 4990044015A; Sat, 24 Jul 2021 10:09:10 -0400 (EDT) Original-Received: from mail01.iro.umontreal.ca (unknown [172.31.2.1]) by pmg3.iro.umontreal.ca (Proxmox) with ESMTP id 16AA444027C; Sat, 24 Jul 2021 10:09:05 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=iro.umontreal.ca; s=mail; t=1627135745; bh=fBGwt6zvR9tb8wp+e7fNndnHjXyXn0PjHf7WKuzU5cw=; h=From:To:Cc:Subject:References:Date:In-Reply-To:From; b=aKIJihN5vNg4EpXQRIsMlA99KNfJvR76meBSzcBqR6q24TRMO2Rfwm0vGxZNGW7YR LL5KKL4E4uFlUZILzuuLE1YTwxSzBG2rvaDrSz9eqX8HwbBbrTpZ6ZyYB7BXw64j/q T30Y7m89g5RhyWKdcTt3ydIKIYIexa1z9tBpLB/YCBQ33r+kMBRyzfvgfmQ+Sk2nCi 6a7XsdGm50ZOSKq8oLB/0eXrkS5lXxLceRlGy+zZ35fp1tcSxpAGgH/oOL8U1JgfHt RMpao9hp+mirAXdXTv9QZ514BP6ysa/+jKpPKMZb+TtPuSVQGqxabSWfnsWIjmbRI0 Rig0HBTGcR5Mg== Original-Received: from alfajor (unknown [216.154.29.138]) by mail01.iro.umontreal.ca (Postfix) with ESMTPSA id D5B921201CF; Sat, 24 Jul 2021 10:09:04 -0400 (EDT) In-Reply-To: <831r7w4yhb.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 17 Jul 2021 20:54:56 +0300") 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.23 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:271541 Archived-At: >> If we copy the buffer's content to a freshly malloc area before passing >> that to TS, then there should be no problem running TS in a separate >> concurrent thread, indeed. > Making a copy of the buffer is a non-starter from where I stand. It > doesn't scale, for starters. I don't see any reason to go to such a > complex design at this early stage. I see absolutely no problem with scaling in making a copy: the extra memory and CPU time taken by the copy will be a constant factor which I don't expect to go much beyond 10%, which doesn't threaten scaling and seems perfectly acceptable in return for being able to perform the parse concurrently. I'm not sure we'll want to do that, but I see no reason to consider it a non-starter. [ BTW, it's not clear to me if an update needs to be able to read the whole buffer or if it only needs access to the "update description". ] Stefan