wlav

I don't understand what part of the above you think is fixed in a future release? They still seem to be local issues? (And I'm working on it; was hoping...

Right, but whatever the reason is, I don't see any of it being fixed by a new release?

LLVM16 is now working on both Linux and Mac. I can't try out on Windows b/c MS is no longer providing evaluation images (https://developer.microsoft.com/en-us/windows/downloads/virtual-machines/). It may again in the future,...

There are still no current VM images from Microsoft, but Windows builds fine in the CI and there are now LLVM16-based wheels as part of 3.5.0.

The segfault should obviously not happen (will fix that); the others are neither here nor there: an empty Python container is not the same as a null pointer. The code...

Interesting, the crash with the `memoryview` is in Python, not in cppyy: ``` if (PyObject_CheckBuffer(pyobject)) { Py_buffer bufinfo; memset(&bufinfo, 0, sizeof(Py_buffer)); if (PyObject_GetBuffer(pyobject, &bufinfo, PyBUF_FORMAT) == 0) { //

The crash is gone with the release of cppyy 3.5.0 and its dependencies. Haven't decided yet on what to do with passing empty arrays, so keeping this open.

Fixed in repo (and leak check test added). The reason for the difference between `list` and `vector` is that `std::vector` has its own ("high performance") iterator. The cause was an...

Fix released with cppyy 3.5.0 and its dependencies.

I don't understand what you are trying to do here? cppyy is a bindings generator between Python and C++. As such, it has state in both languages. With the `scoped_interpreter`...