Rik, I hadn't realised until recently that the Coro breakage caused by consting the MGF vtable array in commit v5.21.7-98-gc910fea, is still unresolved. I propose that we revert this commit for 5.24 (we need another RC anyway for the SvGROW) issue. This should have relatively minimal effect (apart from 4K extra memory usage per process), since all it would be doing is removing a constraint on XS code (the vtable array can now be modified by XS code again). Then post 5.24 we an worry about what changes can be provided by the perl core (e.g. [perl #125439]) that would make it unnecessary for things like like Coro to need to modify the vtable array. -- Nothing ventured, nothing lost.