Emile Cormier comments

Results 281 comments of


                                            Emile Cormier

Support thread safety throughout the API

> My workaround was to create a global mutex and then have wrapper macros that lock that mutex, call the catch macro, and the unlock the mutex. Mutexes are probably...

Support thread safety throughout the API

> TBH, a pub/sub pattern is going to guard its boundaries anyway. Probably internally, i.e. with a mutex. True, but directly using a mutex involves a lot less code than...

Printed seconds precision does not match C++20 spec

@brcha The precision is supposed to match that of the duration passed in. For milliseconds, it should be 3 decimal places. As per the [C++ spec](https://eel.is/c++draft/time.format): > If the precision...

We need a custom executor

> Have tried using the cppWamp library (forked from Autobahn) and it doesn't exhibit this problem, but it doesn't use boost futures. I'd just like to point out for the...

We need a custom executor

See #43

We need a custom executor

I was merely linking this issue to that one. In the experimental [future-api](https://github.com/ecorm/cppwamp/tree/issue003-future-api) branch in CppWAMP, I was able to solve the thread-spawning problem by writing my own [custom executor](https://github.com/ecorm/cppwamp/blob/issue003-future-api/cppwamp/include/cppwamp/asioexecutor.hpp)....

We need a custom executor

Boost.Thread executors and continuations are indeed experimental, and are tagged as such in the documentation. The 1.11.0 development release of the [standalone Asio library ](http://think-async.com/Asio) has added Executor classes as...

We need a custom executor

Asio was updated in Boost 1.66 release. There's mention of executors in this new documentation page: http://www.boost.org/doc/libs/1_66_0/doc/html/boost_asio/net_ts.html I'm too busy with work/life right now to investigate any deeper. Coroutines and...

When attaching a continuation to boost::future, the continuation is executed in a new thread(default), which will cause memory usage problem

multithreading and execution context

See #43, #146, and #156. Asio was updated in Boost 1.66 release. There's mention of executors in this new documentation page: http://www.boost.org/doc/libs/1_66_0/doc/html/boost_asio/net_ts.html . I'm too busy with work/life right now...