json VS tiny-utf8

Shouldn't your benchmark use a somewhat larger JSON? Something from https://github.com/boostorg/json/tree/develop/bench/data, for instance.

The mascot for the library appears to be Jason Voorhees. Should I be concerned?

You should be able to build and include boost json as a standalone subproject in CMake if you are using C++17. (Or also possible to use as header only lib)

It gets far more complicated with C++11, since you also need a ton of other boost modules there.

For more Details you can read the Readme of it. https://github.com/boostorg/json

https://github.com/boostorg/json/blob/f55bd4b85edd9b9b9b2d27fb49d66a990aa89001/include/boost/json/impl/object.hpp#L39

I'm gonna throw this out there - Boost.JSON comes with .natvis visualizers for all of its data structures, so you can inspect all of its types in the debugger and get nice insights: https://github.com/boostorg/json/blob/932b97e5ce899f3faebb7b7ab5a68b023131b77f/include/boost/json/json.natvis

I've recently been trying to use the tiny-utf8 library in Rcpp in order to handle unicode, but I am having serious issues trying to understand how the "wrap" part of it works. For the "as" part, I've received some help on Stack Overflow, which works great, but without a wrap(), it seems that I cannot convert the data type into those of Rcpp. I've been reading this post and trying to replicate it, but with utter failure after long hours, due likely to a lack of knowledge in C++ templates. Could someone give some pointers as to how I might go about doing this? I am at the end of my wits at this point.