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

From: Eli Zaretskii <[email-masked]>
Date: Tue, 29 Sep 2020 07:12:16 +0300

On September 29, 2020 6:29:34 AM GMT+03:00, Richard Stallman <[email-masked]> wrote:
> 
>   > > It is paradoxical, but I think it is correct.
>   > > Equal compares the type of the string, not just the
>   > > characters in it.
> 
>   > No it doesn't. (equal (string-to-multibyte "A") "A") => t.
> 
> I am puzzled, then.  Why DOES the other example return nil?

Because the byte sequences of the two strings are different when there are non-ASCII bytes in the original unibyte string.