Subject: Re: bug#76313: New function `replace-region`

From: Eli Zaretskii <[email-masked]>
Date: Sat, 29 Mar 2025 12:59:28 +0300

> From: Stefan Monnier <[email-masked]>
> Cc: Stefan Kangas <[email-masked]>,  [email-masked],
>   [email-masked],  [email-masked]
> Date: Fri, 28 Mar 2025 11:38:19 -0400
> 
> Any chance we could consider a  breaking change and force a non-nil value of
> one of MAX-SECS or MAX-COSTS before the function is allowed to use the
> costly algorithm?

I'd prefer a completely backward-compatible change of passing a
special value of MAX-SECS to indicate that the potentially costly
algorithm is to be bypassed.