dylanetaft commented on issue #50715: URL: https://github.com/apache/arrow/issues/50715#issuecomment-5121492765
https://github.com/llvm/llvm-project/blob/main/libcxxabi/src/private_typeinfo.cpp _LIBCXXABI_FORGIVING_DYNAMIC_CAST https://github.com/aalexand/sharedlib_typeinfo https://www.qt.io/quality-assurance/blog/one-way-dynamic_cast-across-library-boundaries-can-fail-and-how-to-fix-it I can just find references of people saying libc++ and libstdc++ behave a bit different. libstdc++ relies on symbol names, libc++ relies on a hard ptr comparison. https://en.cppreference.com/cpp/language/dynamic_cast "Some forms of dynamic_cast rely on [run-time type identification](https://en.wikipedia.org/wiki/Run-time_type_information) (RTTI), that is, information about each polymorphic class in the compiled program. Compilers typically have options to disable the inclusion of this information." It seems like a C++ annoyance... -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
