Instance derived from Object deleting all its children before destruction

[MessyGhost]

Godot version

4.2

godot-cpp version

4.2

System information

Windows 11

Issue description

Object::~Object() removes all the children and deletes them before the destructor of the derived class. Shouldn't I delete the children myself?

Steps to reproduce

With the code below, destruction of B may lead to a crash. (In my circumstance, the editor crashes when I open the project the second time)

using namespace godot;

class A: public Node {
    GDCLASS(A, Node);

protected:
    static void _bind_methods() {}

public:
    A() {}
};

class B: public Node {
    GDCLASS(B, Node);

protected:
    static void _bind_methods() {}

private:
    A *a;

public:
    B(): a(memnew(A)) { this->add_child(this->a); }

    ~B() {
        // a is removed and deleted before destruction, either of the below may lead to a crash
        // this->remove_child(this->a);
        memdelete(this->a);
    }
};

def _ready():
	B.new()

Minimal reproduction project

N/A

[MessyGhost]

I just realized that the Object part is destructed before the part of the derived class, which make it nonsense to remove the children in the destructor of the derived class. But it is still confusing that the parent help delete/free all the children.

[AThousandShips]

This is probably a discussion for the main repo as it's not exclusive to extensions, child nodes are deleted in the pre-delete notification

And I'd say it's not a bug but something that should be documented better, if it's not already