Stephen Berry
Stephen Berry
Adding my comments from a pull request to this discussion: I often look at assembly with compiler explorer and benchmark using quick bench. Typically using std::memcpy is the fastest approach...
I think we want to parse from a contiguous buffer anyway, so I don't think the null-termination requirement will be an issue. But, good to note.
Seems relevant to this discussion: [C++23: The rise of new streams](https://www.sandordargo.com/blog/2023/12/06/cpp23-strtream-strstream-replacement)
We should probably also add precompile header testing to the GitHub actions.
I'm converting this to a Discussion. I will gladly accept pull requests that add this feature, but I'm not going to focus on it, because I'd rather focus these kinds...
Great idea!
@jbbjarnason, I added a unit test that doesn't build yet, but I'll keep adding to it to describe the kind of interface we want. I'm thinking of adding custom data...
We should be able to support both compile time and runtime validation. Initially validation should be based off of JSON schema.
There are two approaches to runtime validation. We can perform validation on parse, or we can perform validation on C++ memory. The later will be much more performant and I...
Interesting, thanks for pointing this out. Will address this.