On 10/16/12 10:48 PM, Robert O'Callahan wrote:
On the other hand, for every part of the engine except JS, UTF8 is ideal.
I think it's worth investigating supporting UTF8 strings in the JS engine.
One option: the first time someone calls charAt() or similar on the string,
build an auxiliary UTF16 copy of the string and keep it around.
I talked to Terrence about this a bit today, and he was going to talk to
dmandelin about feasibility... One of the hard parts here is how to not
regress Gecko performance in the process. :(
-Boris
_______________________________________________
dev-servo mailing list
dev-servo@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-servo
