Takatoshi Kondo

It might be helpful: https://github.com/msgpack/msgpack-c/issues/462#issuecomment-216420435

It seems that t is an msgpack::object handle not msgpack::object. Try this: ```cpp auto t=temp.get().type ```

See https://github.com/msgpack/msgpack/issues/164#issuecomment-86368081

https://github.com/msgpack/msgpack-c/wiki/v2_0_cpp_object#conversion msgpack-c has 3 concepts. They are pack/unpack/convert. (Creating object from T is not related in this context) > Can I do something like this? ## pack You can pack...

Thanks you for sending the PR but CI reports errors . After they whould be solved, I will reveiw the PR.

Here is a document: https://github.com/msgpack/msgpack-c/wiki/v_2_0_cpp_json From JSON string to msgpack::object conversion is not directly supported but to msgpack formatted byte stream is supported by JSON for Modern C++. See https://github.com/nlohmann/json/blob/bab5826504ac04695c33954c07ff832fc7b4b2c8/doc/binary_formats.md...

EXT types including timestamp aren't supported but other types output as json. See https://github.com/msgpack/msgpack-c/blob/master/include/msgpack/v1/object.hpp#L396 `[[2,17,1,0,""]]` is json. msgpack::object has visitor interface. See https://github.com/msgpack/msgpack-c/wiki/v2_0_cpp_visitor. This means you can generate any output...

http://stackoverflow.com/questions/40650338/valgrind-on-macos-sierra http://stackoverflow.com/questions/34573039/possible-memory-leak-valgrind-in-osx-el-capitan http://stackoverflow.com/questions/12452541/valgrind-reports-leaked-memory-on-os-x-10-8-1 It seems that valgrind is the tool for linux not macos basically, so valgrind checking should be removed from macos build.

Could you elaborate the question? In addition, if you post a complete and minimal code that describes the issue, it is very helpful. You can use Wandbox for this. See...

msgpack-c class adaptor is mapped to `MAP` or `ARRAY`. It is a design choice. It is not all reason for that, but the base class and derived class could have...