Corey Farrell

@akheron any reason you are against creating a new `json_type` for this (maybe `JSON_RAW`)? My complaint about the current patches is that it expands storage of json_string_t. I realize adding...

In addition to dealing with numbers that cannot be reliably round-trip parsed then dumped I could see JSON_RAW being useful for certain resource constrained situations / performance critical code paths....

I was thinking that JSON_RAW would use json_string_t in the background and thus would not store further information about the contents. In theory we could provide a function `json_type json_raw_typeof(json_t...

I hadn't thought of that, I'm not sure. My idea was that JSON_RAW would be used where the value is not locally interesting, but still needs to be saved to...

@akheron I've done some work on an actual implementation of the JSON_RAW type, I think that the correct way to determine what a `JSON_RAW` contains would be to parse it...

#446 is the last I've worked on this. Unfortunately I've been busy with other commitments lately. Until I get some critical feedback on my PR it's unlikely to see any...

It looks like this is a Windows build. I don't know anything about Windows/Visual Studio so I won't be able to help but I suspect anyone who does know Windows...

`json_loadfd` does not support resuming so using it on non-blocking sockets has a high risk of data loss. I haven't looked into what it would take to support this but...

I'm not in support of making such a change. The problem is that you are providing incompatible CFLAGS to the jansson build. I recommend using the following to configure jansson:...

I wouldn't strongly object but I have to ask what is the use case? Approval really can't happen without seeing code, I would require full test coverage for any new...