Ivan Baidakou

Я хоть и не давно испольюзую (точнее пытаюсь использовать) для side-projects, но по-мне так оба варианта равнозначны: ```cpp (1) ret_value handler(mhood_t); ret_value handler(const mhood_t&); (2) ret_value handler(Msg_Type); ret_value handler(const Msg_Type...

> Поэтому есть альтернативный вариант -- Mercurial-репозиторий на BitBucket-е Есть ещё gitlab: теже фичи что и у github/bitbucket но ещё и с опциональной возможностью развернуть на своих мощностях (не особо...

Hello, I think coroutines support is broken in the latest boost::asio; it does not build on linux too. Try to use Boost `v1.64`.

Sure, go on, PRs are welcome. BTW, the PR to Boost::ASIO might be helpful for you https://github.com/boostorg/asio/pull/55 Another approach - do not use `Coroutines`. Current `bredis` code does not uses...

Derek, `bredis` is header-only library. That means it usually should not build, but just copied the "include" dir right into your project. The build in the sources exists only for...

Hi there, thank you for your proposal. There are drawbacks on your proposal: - it leads to "namespace pollution", i.e. additional methods are injected, but they are not meant to...

Thank you anyway, for your opinion. I'll keep the issue, and may be will apply it later, i.e. after some code stabilization/a few releases.

Good idea! Patches/PRs are welcome :)

@ovanes Here are preliminary experimental PR: https://github.com/basiliscos/cpp-bredis/blob/prepared-command/examples/speed_test_async_multi.cpp it uses `writev` syscall under the hood and performs zero-copy for input commands. but the performance for the bulk of small commands actually...

Sure, you can try `1.66`, but some features like `coroutines` will probably not work.