Windows support without windows.h

[MennoVink]

I recently started porting my project over to asio. Everything was ok and i see the potential... but im now trying to compile on windows.
My project uses PascalCase function names and as such has many conflicts with the ascii/wide defines that asio is leaking (ie DeleteFile from any_io_context.hpp)
Unfortunately ASIO_SEPARATE_COMPILATION does not help in this situation.
I dont see a path to pimpl out any asio usage either as awaitable and executor are needed in headers regularly.
I gues asio as module could work? But that doesn't exist (yet?).

Is there any way i can use asio without it leaking all these preprocessor defines?

[klemens-morgenstern]

No, that's not supported.

[MennoVink]

Would you be interested in a PR where i change all asio self-includes to be relative to their own file?

That will enable a workaround on my side where i create a jumper header that includes asio but undefines problematic leakage. I can then not have asio's include path in the compiler's include paths and make sure none of my code includes asio directly.

[klemens-morgenstern]

I can't decide that, but my guess is no.

[Joker-Principal]

If your project support to use C++20 module, you can write a asio.cppm file, and expose anything you used:

module;
#include <asio.hpp>

export module asio;

export namespace asio {
    using asio::io_context;
    ... // massive using asio::*
}

and use import asio; where you won't the Windows.h included