Rendering functions does not accept custom Vec3

[NicEastvillage]

A QoL feature of v4 is that it is very robust. In v4, all the rendering functions accepts custom vector objects. It just requires that the passed object had x, y, z attributes or was a 3-element list/sequence of numbers. It would be nice if this robustness returns for v5, especially for custom vector types, so you don't have to convert into flat.Vector3 each time.

[VirxEC]

It should work if the type extends the flat.Vector3 class. As for just accepting any vector type with a defined x, y, & z field, I'm not sure how to annotate that in the type system (as imo the proper way to do that would be to extend flat.Vector3).

I do have this example of extending the flat.Vector3 class to add support for the + & * operators: https://github.com/VirxEC/python-interface/blob/140e30a2fb78305733cc2da5cf7786e1e56117cf/tests/render_fun/render_mesh.py#L10-L15

[NicEastvillage]

Okay. I will try that. If there is no performance penalty of the flat struct then that is a fine solution.

[NicEastvillage]

Looks like I can't have a custom constructor. But works otherwise!

[VirxEC]

PyO3/pyo3#1644

[VirxEC]

Basically, this should work:

class SubclassWithExtraInitArguments(SubclassableWithParameter):
    def __new__(cls, bar):
        print("before super new")
        return super().__new__(cls, foo=bool(bar))

    def __init__(self, bar):
        print("before super init")
        super().__init__()