asio icon indicating copy to clipboard operation
asio copied to clipboard

Asio C++ Library

Results 318 asio issues
Sort by recently updated
recently updated
newest added

Hi, I have a question regarding the following code: ``` #include boost::asio::awaitable sleepFor1(const auto& duration) { boost::asio::steady_timer timer(co_await boost::asio::this_coro::executor); timer.expires_after(duration); co_await timer.async_wait(boost::asio::use_awaitable); } auto sleepFor2(const auto& duration, auto&& exec) {...

Hi Chris, I am working on experimental module support for boost and it complains about exporting none-inline global variables. Declaring them inline seems like the correct thing to do anyhow.

In C#, there is a method like this (pseudo code): ```c# class NetworkStream : Stream { ... } class SslStream : AuthenticatedStream { ... } class AuthenticatedStream : Stream {...

When porting my software to boost 1.86.0, I found a strange error that I narrowed down to the following example. `test.cpp`: ```c++ #include int main() { return 0; } ```...

some simple test cases for spawn() with any_completion_handler, deferred, cancellation, and exceptions the second test is a reproducer for https://github.com/chriskohlhoff/asio/issues/1543, and doesn't pass against master

I have loaded the current release (https://archives.boost.io/release/1.86.0/source/boost_1_86_0.7z) and created the following test project: CMakeLists.txt ```cmake cmake_minimum_required(VERSION 3.25) project(ASIO-Test) set(CXX_STANDARD_REQUIRED ON) set(Boost_USE_MULTITHREADED ON) if(WIN32) set(Boost_USE_STATIC_LIBS ON) endif() find_package(Boost REQUIRED) add_definitions(-D_WIN32_WINNT=0x0601) add_executable(Test14...

https://github.com/chriskohlhoff/asio/blob/57577c6db46a4e2de5351af2b185bf52696699a9/asio/include/asio/detail/config.hpp#L45-L71 Here ASIO_DYN_LINK is only useful for windows. This means that on linux, e.g. libfoo.so : defines ASIO_DYN_LINK, includes asio/src.hpp in a file bar : links against libfoo.so, also uses...

Basic sockets, such as `asio::ip::tcp::socket` naturally have an ability to be re-bound to a different context, via `release() + assign()`, using a `native_handle`. That's a great thing in a shared-nothing...