2 Oct
2023
2 Oct
'23
4:57 p.m.
Niall Douglas wrote:
I have received a non-public review which raises concerns about the naming land grab by proposed Boost.Async i.e. a Boost library called "Async" claims too much through its name.
Seeing as nobody here has raised this concern to date, can I confirm everybody here is fine with proposed Boost.Async being called Boost.Async?
If you are not, please suggest a preferred alternative name.
Niall
Boost.Asio.Async, or similar. I'd make a similar argument for other libraries that are highly dependent on ASIO. Regards, Phil.