bug#65451: 30.0.50; `after-change-functions' are not triggered in the same order the changes are made

[Eli Zaretskii]

> From: Ihor Radchenko <yantar92@posteo.net>
> Cc: casouri@gmail.com, 65451@debbugs.gnu.org
> Date: Fri, 25 Aug 2023 08:09:41 +0000
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> >> Elements of the list will be like
> >> [:buffer-chars-modified-tick :region-beginning :region-end-before-edit 
> >> :region-end-after-edit]
> >
> > If you really need buffer-chars-modified-tick, you will have to verify
> > that it is updated before calling the function which updates the
> > "transactions list".
> 
> Do you mean that buffer-chars-modified-tick may not be yet updated at
> the time treesit_record_change is called?

Yes.  You can audit the code and see it for yourself.

> Then, treesit_record_change only uses byte positions. Will it be
> possible to record buffer point positions, or may it be problematic?

Sorry, I don't understand what you are saying here and how this is
relevant to the issue at hand and to my comment in particular.