Re: New optimisations for long raw strings in C++ Mode.

[Eli Zaretskii]

> From: Lynn Winebarger <owinebar@gmail.com>
> Date: Fri, 12 Aug 2022 09:05:06 -0400
> Cc: Alan Mackenzie <acm@muc.de>, gregory@heytings.org, Lars Ingebrigtsen 
> <larsi@gnus.org>, 
>       emacs-devel <emacs-devel@gnu.org>
> 
>  Really?  Then please tell me how is it that we the humans can detect
>  incorrect fontifications even when shown partial strings and comments?
>  We know that fontifications are incorrect, and where strings or
>  comments start or end immediately, just after a single glance.  We
>  never need to go to BOB to find that out.
> 
> Serious question: is fontification intended to display text according to what 
> the author probably intended, or
> according to how a compiler will process that text (leaving correctness to a 
> more precise tool than font-lock,
> whether Semantic, tree-sitter, LSP, whatever)?

I fail to see how this question is relevant to the issue at hand,
which is what should be the behavior of fontification functions in
very large files and files with very long lines.

> Because I can definitely write code that has some subtle issue that I will 
> miss, and erroneously think should
> display one way but which would be processed in a different way.  Should 
> fontification show my likely
> intention (plus, and only for bonus points, possibly highlight the error that 
> disconnects the likely intended from
> the actual parse), or should it display according to the way the tools will 
> interpret it so the author will find
> errors that way? 

Ideally, the latter.  But not at a prise of making moving through and
editing the file impractical.

> When I use a dedicated IDE of recent vintage, it feels  less like I am 
> writing a stream of characters than filling
> in partially constructed objects representing the abstract syntax of the 
> language I'm writing in (with grammar
> that has allowances for incomplete or erroneous constructs), with the text 
> being displayed as a
> representation of the underlying object.  IOW, the relationship of the 
> syntactic object and the text is inverted
> compared to emacs's design, where (if I understand correctly) the properties 
> of the syntactic object are only
> tied to the text through text properties.  With the other approach, the 
> fontification and the syntax object are
> tied together, but with emacs the relationship seems much more tenuous. E.g. 
> completion and fontification
> are completely separate activities as far as I know, though the same 
> contextual information should be useful
> for both activities.

That is correct, for the current Emacs design.

> If CC mode is determining more syntactic information than tree-sitter's 
> incremental parsing provides (per
> Immanuel Lizroth's comment in this thread)

I don't think this is true, FWIW.