NumPy support is a borderline issue for CLIF. Typical usage I saw is the following: C++ has some class(es) that best represented as NumPy arrays. So because th

NumPy support is a borderline issue for CLIF. Typical usage I saw is the following: C++ has some class(es) that best represented as NumPy arrays. So because those classes are specific to the project (not generic like std::) they don't fit into CLIF runtime, but the project supply a C++ library with custom conversion functions as described in ext.md that use NumPy C API tells CLIF that those classes are convertible to Python objects (that NumPy objects are). That all NumPy integration CLIF needs and it has to come from the user.