bug#43598: replace-in-string: finishing touches

[Mattias Engdegård]

27 sep. 2020 kl. 02.34 skrev Lars Ingebrigtsen <larsi@gnus.org>:

> (string-search (string-to-multibyte "o\303\270") "o\303\270")
> => 0
> 
> (string-match (string-to-multibyte "o\303\270") "o\303\270")
> => 0
> 
> (equal (string-to-multibyte "o\303\270") "o\303\270")
> => nil

(compare-strings (string-to-multibyte "o\303\270") nil nil "o\303\270" nil nil)
=> t

I'd say it's equal, string-equal, string-lessp and string-greaterp that are odd 
and that we probably should fix if it can be done without making them slower. 
Unless, of course, we can come up with an alternative theory of operation that 
is satisfactory.

> But I guess we've lived with this for...  decades?  So that's probably
> OK.

Yes, there is no hurry.