Re: Why does using aset sometimes output raw bytes?

[Stefan Monnier]

>> It's not the implementation, but the semantics of unibyte/multibyte
>> strings presumes that the difference doesn't matter much for ASCII-only
>> strings, which is mostly true but isn't true in the case of `aset`.
> The same is true about concat, btw.

I think it's less severe (`aset` can end up changing (by side-effect)
a unibyte string to multibyte, i.e. changing the nature of the object,
which I believe is the only time we do something like that), but yes
similar problems appear elsewhere (hence the "mostly" above).


        Stefan