Re: (aset UNIBYTE-STRING MULTIBYTE-CHAR)

[Stefan Monnier]

>> > > That inefficiency may or may not be important in any given context.
>> > > Fixing it in casefiddle is definitely desirable.
>> > > But is it worth breaking all such packages just so that they
>> > > will optimize an operation that might not use much of the time anyway?

>> > Why work around the problem in `aset' if it isn't worth fixing in the
>> > original code?

>> But you wrote:

>> > > Then, shouldn't we start the experiment of inhibitting aset
>> > > on strings just now?
>> > 
>> > But I do not think we're ready for that.  Maybe 10 years from now...

>> I want to avoid treating non-ASCII chars different from
>> ASCII.  Then, the only solution is to make aset work well
>> for multibyte characters.

> The attached simple change does the work.  May I install it?

I guess it's OK.  It's pretty ugly in terms of code, but in terms of
behavior it more or less matches the behavior of what I use (where
I distinguish between unibyte/anybyte/multibyte),


        Stefan