чт, 31 июл. 2025 г. в 09:53, Artyom Beilis via Boost <boost@lists.boost.org>:
So quick google (and their gemeni) leads to examples exactly what I need: bp::child, wait, terminate, wait_for etc. Lots of tutorials fine.
This thread is actually amazing. We shouldn't change our APIs, because LLMs can get confused and hallucinate wrong snippets of code. Another point I also liked a lot is this:
No grace time, no deprecation, no keeping old API for a while (replacing headers with v1 is not backward compatibility it is a workaround) And honestly including huge dependency on Boost.Asio without "asking" is a problem.
The "no grace time, no deprecation" was immediately contradicted by the next email. The "including Asio dependency" looked very strange to me, as I vaguely remembered that Asio was always a dependency of Process. Luckily, we have Boost dependency reports online: https://pdimov.github.io/boostdep-report/boost-1.66.0/process.html. The key takeaway for me is that when asked for "concrete projects where that has been a problem" you came up with a *hypothetical* that you didn't even think through very well.