Results 358 comments of Takatoshi Kondo

Here are example source files and CMakeLists.txt. The following line might help you. https://github.com/msgpack/msgpack-c/blob/c_master/example/CMakeLists.txt#L22 You can also try https://github.com/msgpack/msgpack-c/tree/c_master#install-from-git-repository instruction.

It seems that the issue is caused by your code not msgpack-c. I cant help you any more.

When I use `boost::type_erasure::any`, especially as the member of the container, I got annoying outputs as follows: ``` boost::type_erasure::any_constructor_control> = {

@YoDaMa , @ogis-yamazaki and I are working on the same project that uses MQTT.js. I reviewed the original version of the PR and I noticed that it is NOT an...

I find the way. My first try was: ```cpp #include #include namespace sml = boost::sml; struct ev1 {}; struct with_prop; struct table { auto operator()() const noexcept { using namespace...

I found a better solution. Defining operator()() as a member function template. I don't need to separate declaration and definition:) ```cpp #include #include namespace sml = boost::sml; struct ev1 {};...

Finally, I eliminate function object! The inner lambda expression with `auto` parameter and explicit return value type make the body of lambda expression instantiation lazily. ```cpp #include #include namespace sml...

I noticed that some of my solutions depend on undefined behavior of the compiler. That means the code is ill-formed. See https://stackoverflow.com/questions/58246088/lazy-instantiation-for-lambda-expression https://github.com/boost-experimental/sml/issues/93#issuecomment-283629397 and https://github.com/boost-experimental/sml/issues/93#issuecomment-283630876 are compiled and worked as...

Let me explain what the problem is. You might think I can place member functions in `table` directly. I can do that. But the member function can be called only...

I tried to find a different way. Instead of inject my data, perhaps there is a way that somehow extract my data from the state machine. I found the following...