> From: Alex Bennée <alex.ben...@linaro.org>
> Cc: Stefan Monnier <monn...@iro.umontreal.ca>, 23...@debbugs.gnu.org, 
> rpl...@gmail.com, jwieg...@gmail.com, nljlistb...@gmail.com
> Date: Tue, 19 Jul 2016 18:05:37 +0100
> > Do we care that using save-match-data in every call to replace-match
> > might mean a performance hit?  If it will, then this will again punish
> > most of the users for the benefit of those few who (1) have
> > buffer-modification hooks, and (2) those hooks call save-match-data.
> I care unless there is an easy way to identify which buffer modification
> hooks are responsible so I can take steps as a user to mitigate the
> problems.

Any hook in before-change-functions or after-change-functions that
calls save-match-data.

If we care about the performance hit, we need to come up with a
different solution for this problem (or measure the performance hit
and convince ourselves it is not a big deal).

Reply via email to