From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: How to add pseudo vector types Date: Fri, 23 Jul 2021 08:21:02 +0300 Message-ID: <838s1x38sh.fsf@gnu.org> 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> <8335s64v10.fsf@gnu.org> <5380C92B-6C15-4490-A1E0-1C3132DBB16A@gmail.com> <878s1yigle.fsf@telefonica.net> <83im122s2n.fsf@gnu.org> <874kcmi1vl.fsf@telefonica.net> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="16802"; mail-complaints-to="usenet@ciao.gmane.io" Cc: emacs-devel@gnu.org To: =?iso-8859-1?Q?=D3scar?= Fuentes Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Fri Jul 23 07:22:06 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 1m6ndO-0004B2-7B for ged-emacs-devel@m.gmane-mx.org; Fri, 23 Jul 2021 07:22:06 +0200 Original-Received: from localhost ([::1]:38324 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1m6ndN-0002bg-8v for ged-emacs-devel@m.gmane-mx.org; Fri, 23 Jul 2021 01:22:05 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:37150) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1m6ncf-0001vs-V3 for emacs-devel@gnu.org; Fri, 23 Jul 2021 01:21:21 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:46568) by eggs.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1m6ncf-0003m9-0K; Fri, 23 Jul 2021 01:21:21 -0400 Original-Received: from 84.94.185.95.cable.012.net.il ([84.94.185.95]:1954 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1m6nce-0004ga-I8; Fri, 23 Jul 2021 01:21:20 -0400 In-Reply-To: <874kcmi1vl.fsf@telefonica.net> (message from =?iso-8859-1?Q?=D3scar?= Fuentes on Thu, 22 Jul 2021 21:29:02 +0200) 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:271484 Archived-At: > From: Óscar Fuentes > Date: Thu, 22 Jul 2021 21:29:02 +0200 > > >> Guys, you are speculating too much about minutia and worst-case > >> scenarios. (Do we really care about TS not supporting files larger than > >> 4GB? I mean, REALLY?) > > > > Yes, we do. For at least 2 reasons: (a) source code files produced by > > programs can be very large; > > I know, I work with machine-generated (read: code-dense) 20+MB C++ files > on a regular basis. > > However, I wouldn't agree on renouncing to useful features because they > could be problematic when dealing with large files. That is, it would be > a mistake to discard TS as inadequate for Emacs just because it doesn't > benefit (and I say "not benefit", not "penalise") certain use cases. It was not my intent to say we should discard TS as inadequate because of these limitations. What I meant is that we should know about the limitations and plan in advance how to handle them when a user bumps into them. Disabling TS-related features could be one such mitigation, but maybe we could come up with smarter fallbacks. It sounds like the rest of you message was to convince me not to give up on TS, in which case there's no need: I'm convinced already, and mostly agree with what you say. > Talking about scenarios of heavy memory usage, I'll comment in passing > that in my recent experience, once Emacs exceeds 2GB the gc pauses start > to be so annoying that I don't care anymore about how much memory an > external tool would use if it works fast enough. That's a separate issue. And the amount of memory GC has to scan is not directly related to the memory footprint of the Emacs process. So I would be interested in seeing the results of memory-report in those cases where GC takes too long (in a separate thread, please).