Stephen Berry

We do need full end of buffer checking for open APIs, so this issue will be fully addressed in the future. In the meantime I have added warning about using...

End of buffer checking is now incorporated with the changes that no longer require null termination.

Serializing to a pre-allocated buffer versus a dynamic buffer like `std::string` typically has less than a 5% difference in performance. Furthermore, in inter-process communication you should typically reuse your serialization...

I see. I'll keep this issue alive to add the ability to compute the space required before serialization. I typically use shared libraries which allow me to share the std::string...

I'll have to come back to this, but note that Glaze does not automatically reflect your enum. Meaning it will treat your enum values as integers by default. Use a...

Are you trying to build the latest version or the `main` branch? I'll see if I can try to replicate this.

@HumaNOOO, do you have the standards compliant preprocessor flag? From the documentation: MSVC Compiler Flags Glaze requires a C++ standard conformant pre-processor, which requires the /Zc:preprocessor flag when building with...

I'm glad that was it. I really wish MSVC would default to standard compliance, at least in new versions, but alas.

Yes, this should be renamed to `get_monotonic_enum_name`. But, it isn't used generally for enum handling in Glaze. Thanks for reporting this, the plan is to overhaul the enum handling in...

@amosbird, dynamic partial writing is definitely desired. A long term goal is to support JMESPath, which would also require this support. The reflection system in Glaze already provides an array...