Can we also have a build option to deliberately keep the old situation?
Or else my code will cause crashes where it is checking the returned pointer as soon as this gets merged.
And right now I cannot change the code to callnew(std::nothrow) as it is not yet merged.
I may need to make a macro for it or else my code will become quite messy while I still want to support old and new core libs.

new (std::nothrow) is currently supposed to work. Did you try it ?

@TD-er the whole point of this PR is to clean up the current situation and better conform to the C++ language standard. That means removing the legacy behavior.
Although this is expected to be merged soon, you have ample time to migrate, assuming you really need it.
@d-a-v 's question is valid: new(std::nothrow) is supposed to work now. If it doesn't, We Need To Know.

I have not tried it yet.
I just assumed it wouldn't because this PR implemented it...

I will try to see if it compiles using the current core code and will start making a macro for it.

OK, next time I should try it first before panic.
It does compile just fine, and the changes do appear quite easy to do in my code (not that manynew calls)

Thanks for this, finally this is cleaned up!