What's wrong with this code?

[Emaer]

@ShiftZ

Object in the ‘MyActors’ array can not be destroyed at any time. Spawned actors are possessed by the world.
Why aren't spawned Actors without reference garbage collected? - Programming & Scripting - Epic Developer Community Forums

Do you agree?

Very likely. I get confused about it sometimes.

@ShiftZ

I’ve given an example of a well known function that can fail but never returns a null pointer - opeator new.

By default operator new throws exception, but you can use overload (std::nothrow) which return nullptr on fail.

@"ShiftZ

But tell me how did you come to the conclusion that I must check the pointers for null? Since when do raw c++ pointers become null if the object they points to is destroyed? In the real world pointers to destroyed objects become invalid and a simple check for null wont give you a false value. That’s why there is no reason to check it for null once they were put into the array.

You’re absolutely right, but this is true for pure C++.
Epic had the ridiculous idea to add GC to cpp. And thanks to this, the ubiquitous checking of nullptr, the lack of information about who owns the resource, behind-the-scenes nulling, etc.