Option to use partial with char* or char[] about glaze HOT 7 CLOSED

Thanks for bringing up these issues with raw and std::string_view buffers. I'm about to merge a major change to support errors when writing and then I'll prioritize these issues.

from glaze.

Support has been merged, let me know if you run into any issues.

from glaze.

This was just overlooked for partial writing, so I'll add in a function that supports raw buffers.

I actually need to make some write API changes to better support handling write errors. I'll probably include this support in that merge.

I'm curious, do you know your sizes? Could you be using std::string_view?

from glaze.

As far as knowing sizes:
JSON tags: yes
JSON values: no

so it'll look like this for one partial
{"name": "John Smith"}

and this for another and so on.
{"address": "123 North Str"}

so the size of the JSON needs to be variable, but we're just allocating enough memory up front to hold anything we would ever serialize and using a buffer + an offset to determine the size of the buffer content we care about.

I get a different issue when using std::string_view interestingly:

/include/glaze/json/write.hpp:1326:38: error: could not convert ‘quoted_key’ from ‘const std::basic_string_view<char>’ to ‘long unsigned int’
 1326 |                      dump<quoted_key>(b, ix);
      |                      ~~~~~~~~~~~~~~~~^~~~~~~
      |                                      |
      |                                      const std::basic_string_view<char>

where my call to write_json is as follows

char buf*;
std::string_view svOut{buf};
glz::write_json<partial_1>(msg, svOut);

from glaze.

Support is being added in #1074

from glaze.

std::string_view is read only, so I've decided to just support char* and char[] raw buffers for writing. I could add write support for std::span<char>, but this might add some confusion and I don't feel is necessary.

from glaze.

Awesome, I will definitely check it out soon. Thanks!

from glaze.