Fix marshal to not have excessive token escape.
Sizable performance impact. Recently added scalable benchmarks helped point this out. (Arguably, certainly, I could've/should've seen this one earlier; it's honestly pretty "duh". But somehow it never got priority attention. A benchmark is still awfully useful for directing attention!) With this, the new node marshal is looking *really* snazzy. Most of the allocations remaining there are just iterator creation... and we have a plan to amortize those out of existence, too. But I'm going to save that one for later.
Showing
Please register or sign in to comment