Possible raylib bindings vector type optimisation?

[MaxBeaud]

Is there a particular reason why the vector types in the bindings do not take advantage of native C3 vector type?

These types:

struct Vector2 @compact
{
    float x;                // Vector x component
    float y;                // Vector y component
}

struct Vector3 @compact
{
    float x;                // Vector x component
    float y;                // Vector y component
    float z;                // Vector z component
}

struct Vector4 @compact
{
    float x;                // Vector x component
    float y;                // Vector y component
    float z;                // Vector z component
    float w;                // Vector w component
}

can become:

def Vector2 = float[<2>];
def Vector3 = float[<3>];
def Vector4 = float[<4>];

I would ask the same question about the Matrix type in the bindings not using the std::math::matrix implementation, but I haven't tried that one, and there my be some ordering difference not sure. Plus it it wont work in a no-std context.