ZDoom

[quote=Apeirogon post_id=1228771 time=1662895858 user_id=20629]
Ah yes, everything is a pointer in zscript...
Why it works with zscript arrays than?! array<int> list[3] supports list[0].push(1) without crashing.
[/quote]
Because not everything is a pointer in ZScript. It's just classes that are reference types, much like C# and Java. Ints, floats, strings, vectors, structs and dynamic arrays are all value types.

Ah yes, everything is a pointer in zscript...
Why it works with zscript arrays than?! array<int> list[3] supports list[0].push(1) without crashing.

These aren't comparable. Classes in ZScript don't work the same way as in C++, they're always references, never values.
[c]test whatever_stack[10];[/c] is an array of class instances on the stack, [c]test * whatever_heap = new test[10];[/c] is an array of class instances on the heap. Neither is equivalent to the ZScript example in the OP, which is an array of pointers to class instances. The C++ version of [c]vector_wrapper vec [3];[/c] in your example would be [c]vector_wrapper *vec [3];[/c].

Unless we talking about different things, c++ do this.
https://godbolt.org/z/Kq4Y33qfM
Yes there are hidden obligatory constructor calls, but point is, its not like in zscript static array are just a malloc call and thats it.

This is working exactly as it should. The compiler can't and shouldn't automatically create class instances for you, no language I'm aware of does that.

This seems like a bad idea. If I wanted implicit initialization, I'd use a struct instead.

class debug_build : eventhandler
{
    vector_wrapper vec[3];

    override void NetworkProcess (ConsoleEvent e) 
    {
        if(e.name == "bug")
        {
            vec[2].a.push(13);
            console.printf(""..vec[2].a[0]);
        }
    }
}

class vector_wrapper
{
    array<int> a;
}

class debug_build : eventhandler
{
    array<int> vec[3];

    override void NetworkProcess (ConsoleEvent e) 
    {
        if(e.name == "nobug")
        {
            vec[2].push(13);
            console.printf(""..vec[2][0]);
        }
    }
}

Probably more 'missing feature' than 'bug'.

C like arrays (type name[number]) are missing implicit instantiation of an objects if its type is a user defined object.
Next code
[code]
class debug_build : eventhandler
{
vector_wrapper vec[3];

override void NetworkProcess (ConsoleEvent e)
{
if(e.name == "bug")
{
vec[2].a.push(13);
console.printf(""..vec[2].a[0]);
}
}
}

class vector_wrapper
{
array<int> a;
}
[/code]
would produces 'address zero' vm crash on line with push directive.

However this code
[code]
class debug_build : eventhandler
{
array<int> vec[3];

override void NetworkProcess (ConsoleEvent e)
{
if(e.name == "nobug")
{
vec[2].push(13);
console.printf(""..vec[2][0]);
}
}
}
[/code]
works fine and print 13 into console.

Test example
[attachment=0]c_like_array_bug.zip[/attachment]
Start a new game and type into console 'netevent bug' for a first version and 'netevent nobug' for a second.