Max

What's more - what if resumed coroutine throws an exception? async_mutex_lock releases async_mutex in destructor via calling mutex->unlock() So there is potential undefined behavior

Hi! Have just looked through the source code - channels are not bound to coroutines, that is just an example. I believe you can easily use them with callbacks, futures...

Well, VS2013 for sure uses too old compiler... If it doesn't -> force it to use at least C++17 std::variant requires c++17, 'auto' return type without trailing type requires at...

According to this declaration from source code: ``` /// Asynchronously send a message. template auto async_send(ASIO_MOVE_ARG(Args)... args, ASIO_MOVE_ARG(CompletionToken) token); ``` It must be asio::error_code in case of standalone asio or...

@toprak1224 install python 3 from official resources and perhaps during the game shift+tab and run this file saved as .py

@toprak1224 I guess you don't need to edit the file, but if you have already downloaded and installed python3, then go to command line and type 'pip install pymem' Then...

I have encountered the same behavior with onerror websocket handler which was called right after onclose. Probably crow::websocket::connection object is not valid at that point...

I join the question, are you @chriskohlhoff planning to add something like [async_mutex](https://github.com/lewissbaker/cppcoro#async_mutex) from [cppcoro](https://github.com/lewissbaker/cppcoro)? It's not about thread synchronization, but about prevention of concurrent execution of coroutines at some...