Stephen Berry

Thanks for finding a workaround! But, it does look like a fix has been implemented. So, I'll probably just wait for that.

There is currently no C++ WS client, but I'll work on adding one. I typically use frontend websocket clients, but I see the usefulness for a C++ implementation. Do you...

Initial websocket client code has been merged into `main` and documentation is here: https://stephenberry.github.io/glaze/networking/websocket-client/?h=webso - #2071 Supports TLS as well. Please report any issues or pains in using it!

Thanks for the encouragement! And, thanks for explaining this issue in detail. I recently opened the issue #1019, which concerns adding reader/writer structures for incremental parsing. I think supporting these...

Thanks for pointing this out. The plan is to make the glz::context more generic, which would allow custom error messages, and I'll also take missing keys into account. We should...

I think we want to report all keys that are missing. This would be easiest to handle as a `std::vector` of all missing keys. However, I don't generally want this...

Adding notes for future implementation: I think the best way to handle missing keys in structures is to pass around a uint64_t, where each bit indicates an index for whether...

Now that we have `custom_error_message` as part of the output for `glz::format_error`, I decided that a straightforward solution is to just report the first key that is missing. I should...

Thanks for these notes. I'm currently occupied for a few weeks, so I won't get to this immediately. But, I'll try to address this as soon as I'm able.

Awesome! I looked over it briefly and I'll plan to go over it again after I've given it more thought, but I really like this syntax as a starting point...