On 3/15/22 15:24, Peter Maydell wrote:
On Tue, 15 Mar 2022 at 14:09, Stefan Hajnoczi <stefa...@redhat.com> wrote:
Also, once C++ is available people will
start submitting C++ patches simply because they are more comfortable
with C++ (especially one-time/infrequent contributors).
This to my mind is the major argument against using C++
for coroutines...
I agree on the need for a policy, but _what_ C++ are they going to be
contributing that we should be scared of? We're talking about:
* major features contributed by one-time/infrequent participants (which
is already a once-in-a-year thing or so, at least for me)
* ... in an area where there are no examples of using C++ in the tree
(or presumably the maintainer would be comfortable reviewing it)
* ... but yet C++ offer killer features (right now there's only C++
coroutines and fpu/)
* ... and where the one-time contributor has put enough investment in
using these killer C++ features, that telling them to remove the
features would amount to a rewrite.
That does not seem to be a common situation, and not even a problematic
one if it were to happen.
Paolo
