Re: Intent to ship: accumulating most JS scripts' data as UTF-8, then directly parsing as UTF-8 (without inflating to UTF-16)

On 8/6/19 8:16 AM, Anne van Kesteren wrote: > On Sat, Jul 20, 2019 at 2:05 AM Jeff Walden wrote: >> (*Only* valid UTF-8: any invalidity, including for WTF-8, is an immediate >> error, no replacement-character semantics applied.) > > Wouldn't adding this allow you to largely bypass the text

Re: Intent to ship: accumulating most JS scripts' data as UTF-8, then directly parsing as UTF-8 (without inflating to UTF-16)

On Sat, Jul 20, 2019 at 2:05 AM Jeff Walden wrote: > (*Only* valid UTF-8: any invalidity, including for WTF-8, is an immediate > error, no replacement-character semantics applied.) Wouldn't adding this allow you to largely bypass the text decoder if it identifies the content to be UTF-8?

Re: Intent to ship: accumulating most JS scripts' data as UTF-8, then directly parsing as UTF-8 (without inflating to UTF-16)

On 7/20/19 4:41 PM, Nicholas Nethercote wrote: > This is excellent news. Do you have any measurements showing perf effects? Perf changes should have first become visible with the landing of bug 1554362. There was one quasi-automatically-reported perf improvement, on the Sheets raptor test:

Re: Intent to ship: accumulating most JS scripts' data as UTF-8, then directly parsing as UTF-8 (without inflating to UTF-16)

This is excellent news. Do you have any measurements showing perf effects? Semi-relatedly, Swift 5 will change the preferred encoding of strings from UTF-16 to UTF-8. Some readers might find the accompanying blog post interesting: https://swift.org/blog/utf8-string/. Nick On Sat, 20 Jul 2019 at

Intent to ship: accumulating most JS scripts' data as UTF-8, then directly parsing as UTF-8 (without inflating to UTF-16)

# Intent to ship: UTF-8 parsing of external