Tamás Szelei

If I understand correctly, that is a third option: `then` as a free function. But I also found that `boost::future` can provide a `then` function. So I'll probably use that.

This is by design and it *has to* change. A sensible default config.h is included in the rpclib source for people who just blindly copy the library include dir. But...

Hmm, I just realized an issue with ignoring the file. I will want to a) keep it in the repo and b) occasionally modify it. I don't know if git...

I disagree, but I'm open to suggestions if you think this is a design issue. The way I see it, the alternative is to not have config.h, only config.h.in in...

Having a config.h file is not something exotic that rpclib made up and certainly not a design problem. Libraries are unlike standalone applications in that they need to adapt to...

> Again, from my naive/personal experience, I don't think this config.h should be modified during the build. I only have anecdotal evidence as well to counter that, so let's remove...

That's still friction, it still needs those defines. It still lets you build with incorrect flags, too (there is no way to verify at compile time that the library was...

Thanks for taking a look. I meant to remove those examples because the "basic" example is the calculator. But I might keep them with your fix, after all. I'm currently...

Thanks for the stack trace. This is probably a race condition (might be related to a few other recent reports).

@sytelus I hear that, and it was originally done for that exact reason. However, this abstraction is leaky and causes an active disadvantage for some users. Now, if you are...