To be honest, xs (and xs_json too) is infact what I liked most of #snac2 codebase: a non-conventional approach optimized for the specific use case.

Having said that, it looks trivial to modify _xs_json_load_lexer, xs_number_new, xs_number_get, xs_number_str to store/retrieve the double as a null terminated char[sizeof(double)+1].

I just wonder if it's worth the performance gain, tbh.

@lizzy@social.vlhl.dev @ada@zoner.work @kimapr@ublog.kimapr.net

in fact it doesn't cause any issue: #snac2 is likely the lightest and best performing #fediverse server out there.

@rozenglass@fedi.dreamscape.link @lizzy@social.vlhl.dev @ada@zoner.work