Subject: bug#61369: Problem with keeping tree-sitter parse tree up-to-date

From: Eli Zaretskii <[email-masked]>
Date: Sat, 18 Feb 2023 09:15:56 +0200

> Cc: Theodor Thornhill <[email-masked]>, [email-masked]
> Date: Sat, 18 Feb 2023 02:11:22 +0200
> From: Dmitry Gutov <[email-masked]>
> 
> I'm not sure whether there is an actual hard limit on modifying the
> text outside of the current restriction.

It is, for most/all practical purposes.  If you try to modify text
outside of the current restriction, you risk many parts of code
barfing or signaling errors on you.  For example, conversion from
character to byte positions and vice versa will stop working (and in a
build with --enable-checking will actually raise SIGABRT).