From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.ciao.gmane.io!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: [SPAM UNSURE] Re: Reliable after-change-functions (via: Using incremental parsing in Emacs) Date: Fri, 03 Apr 2020 10:47:50 +0300 Message-ID: <83y2rdvwm1.fsf@gnu.org> References: <83369o1khx.fsf@gnu.org> <83imijz68s.fsf@gnu.org> <831rp7ypam.fsf@gnu.org> <86wo6yhj4d.fsf@stephe-leake.org> <83o8sax803.fsf@gnu.org> <86pncpffmk.fsf@stephe-leake.org> Injection-Info: ciao.gmane.io; posting-host="ciao.gmane.io:159.69.161.202"; logging-data="32764"; mail-complaints-to="usenet@ciao.gmane.io" Cc: emacs-devel@gnu.org To: Stephen Leake Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Fri Apr 03 09:48:36 2020 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 1jKH47-0008R3-LB for ged-emacs-devel@m.gmane-mx.org; Fri, 03 Apr 2020 09:48:35 +0200 Original-Received: from localhost ([::1]:51516 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jKH46-0002P8-NA for ged-emacs-devel@m.gmane-mx.org; Fri, 03 Apr 2020 03:48:34 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:40569) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jKH3c-0001yt-JF for emacs-devel@gnu.org; Fri, 03 Apr 2020 03:48:05 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:47788) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1jKH3c-0005rl-B5; Fri, 03 Apr 2020 03:48:04 -0400 Original-Received: from [176.228.60.248] (port=1926 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1jKH3b-0003mh-G9; Fri, 03 Apr 2020 03:48:04 -0400 In-Reply-To: <86pncpffmk.fsf@stephe-leake.org> (message from Stephen Leake on Thu, 02 Apr 2020 18:49:07 -0800) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] 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:246309 Archived-At: > From: Stephen Leake > Date: Thu, 02 Apr 2020 18:49:07 -0800 > > > I think we should try to avoid both copying and encoding the text we > > send to the parser. Both operations are expensive and require memory > > allocation. > > I don't understand what the alternative is. The parser imposes the > reasonable requirement that the input text be utf-8 (or possibly some > other standard format). Emacs raw buffer text is not utf-8, so we must > do some encoding. Emacs represents buffer text as a superset of UTF-8, with the violations of strict UTF-8 being very rare in buffers that hold program sources. The function we can provide that lets tree-sitter access buffer text can cope with those violations, if it turns out that tree-sitter cannot do that by itself (which frankly, I'd expect it to be able to do).