Are UTF8-backed (as opposed to Latin1-backed) JS strings with random access going to be a real possibility in SpiderMonkey? It’s obviously possible to make random access work with an appropriate indexing data structure, but popular JS benchmarks are pretty sensitive to string performance.
Cameron On Jul 7, 2014, at 7:01 PM, Robert O'Callahan <rob...@ocallahan.org> wrote: > I'm excited about pushing UTF8 as far as possible! > > One thing not mentioned in the notes is that Spidermonkey is adding Latin-1 > string support, so hopefully it will be pretty easy to avoid converting > ASCII-only strings at WebIDL boundaries. It would certainly be ideal if > Spidermonkey eventually supports UTF8 directly. > > If you want to, it's easy enough to encode lone surrogates in UTF8. Just > encode the UTF-16 code point as if it was a real character. > > Rob _______________________________________________ dev-servo mailing list dev-servo@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-servo
