wlav

There was apparently indeed no check on this path (goes through `initializer_list`) for new-style buffers (as numpy uses). That's now fixed in repo. However, I chose to simply reject this...

There are a ton of ways of initializing a `std::vector`: it supports the full `tuple` test suite. If the type of the data that came directly from the camera wasn't...

That's indeed an omission, which probably never showed up b/c the double meaning (`nullptr` v.s. empty) is not common. Is fixed in repo.

Looks like somewhere deep inside of Cling (or even Clang, to be honest) an assumption of a virtual dtor existing is being made, but `Common` does not have one. I'll...

That last error is separate from the problem of the using: `nullptr` pointer is simply not accepted for `T* const&`, whereas the typed pointer is. But yes, `TypedefPointerToClass` should have...

The original issue is fixed in repo.

`cppyy.nullptr` is a unique Python object, so that it can be pointer compared, which is nice and fast. It's not a `CPPInstance` type, which you get by binding `nullptr`. The...

If `_cppyy` isn't available, then it hasn't been enabled by upstream yet. Indeed, looking in the `pypyoptions.py` file, I see: ``` # not ported yet if IS_64_BITS: for name in...

I'm trying to create a self-contained reproducer, but it all works for me: ``` import cppyy, ctypes cppyy.cppdef("""\ namespace enum_passing { typedef enum LogicType { LOGIC_TYPE_BOOL = 0, LOGIC_TYPE_BIT =...

Is this the same enum as in #4? (I.e. the one that establishes that yes, indeed, the enum type is `unsigned int`?) Actually, I just remembered ... cppyy-bound enum types...