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.
akkoma flavored lizzy (fleckenstein@lizzy.rs) (npub13qr…egvc) :neptune: *Ada - Np-93/237 :neobot_box: (npub1mhv…8s5z) kimapr ☭ 🇺🇿 ⚧ ⚢ ❤️🧡🤍🩷💜 (npub1x2y…8qaj)
