Dmitry

Yeah, extra info is necessary to investigate this issue.

When we use `detail::value_type`, that is for conversions.

```c++ value foo(); void bar(string) bar(foo().as_string()); ``` This will copy the string. With an rvalue-ref overload it wouldn't.

Merged via a0388eae9b36bded31fa874185e728128ace777c

Can you provide an example of code that leads to garbage at runtime? The conversion from object to value should work properly.

I'm not principally opposed to the idea of supporting JSON Patch, but our current priorities are with different things. So, the quickest way to get this functionality is to write...

## DOCUMENTATION 1. [ ] 1. Add reference to RFC 7159 (https://www.rfc-editor.org/info/rfc7159). It allows implementations to set limits on the range and precision of numbers accepted. 2. [x] 2. The...

My comments on unaddressed items: Documentation 1. Created issue #742 5. Created issue #743 6. Currently Docca only supports tying a free function to a class via friend declaration. We...

I don't believe users need to do that, though. And we now have a special function to create `result` that stores an `error_code` with `generic_category` (Peter asked for it).

Indeed, you are correct. The possible solution that I see is 1. Add a trait that establishes the value of the underlying type that corresponds to all flags set. By...