On 22 Aug 2025 09:10, Vinnie Falco via Boost wrote:
On Thu, Aug 21, 2025 at 7:22 AM Christian Mazakas via Boost < boost@lists.boost.org> wrote:
Chris could improve this dramatically here.
Yes, for example:
https://original.boost.org/doc/libs/1_89_0/doc/html/boost_asio/reference/asy...
High quality documentation, that is. How many years has async_initiate been in Asio? Emails and GitHub issues go unanswered. Who is going to bother doing the work for a PR without some kind of assurance that there will be an interaction? This entire thread is going in a very predictable direction where everyone explains why a fork is a bad idea and suggests that people write new things which are not forks, yet there is nothing actionable to solve the fundamental problem which is that we have a perfectly working and well maintained library yet the aspects where it interfaces with the public are utterly lacking. My proposed solution is a fork and the only other answer which addresses the stated problem has been "its fine the way it is" (and this is most certainly incorrect, see link above).
The discussion showed that at least some issues and PRs are handled. Did you or anyone else try submitting a PR adding the missing documentation?