wlav

I remember something similar like this one, where a string constructor is selected; can't find that bug report quickly (bit of a mess here with a big conference next week)....

Upstream is working on Clang13 (https://github.com/vgvassilev/cling/tree/cling-patches-llvm13). If memory serves me, there are ~40 tests still failing, so still some work on their end. Apparently from that v13 on APIs are...

These guys are hard to pin down, September is rumored: https://github.com/root-project/root/pull/10294 Myself, I'm too pre-occupied with Numba atm. to try out LLVM 13 (cppyy only needs a smaller subset, so...

That's an issue unique to global variable pointers: the wrapper proxy is a to an `A**` (that is, `&a`) to ensure that updates to the global pointer on the C++...

Sorry, didn't see the update. That said, `cppyy.ll.dynamic_cast["B"](cppyy.gbl.a).helloB()` (the original problem) works fine for me. So the issue is only if return as an `intptr_t` and use of `bind_object`? Yes,...

I don't understand ... `makeAB()` in the code above returns `intptr_t`: ``` intptr_t makeAB() { A *a = new B(); return (intptr_t)reinterpret_cast(a); } ``` so it should not be possible...

That symbol is lives in `libCoreLegacy.so`, which should certainly not be linked with, so I'm not understanding that step. Could you give the PyPI M1 builds a try instead (`python...

Seems to me that the only way it can fail if the libraries are available in PATH, if there is a 32b/64b mismatch? (Given that the names are explicit 64.)...

The found class really has no methods as far as the bindings generation is concerned. If instead of `template struct Test2 { };`, `template struct Test2 { };` is used,...

Seems to be caused by `Executors.cxx` doing `#include ` instead of `#include ` and thus bringing in the C rather than C++ headers. Is fixed in repo (https://github.com/wlav/CPyCppyy/commit/bf37247f9b72c3b14e673ed24a7a3628a2da2750). Not sure...