You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Full background can be found on the linked discussion pybind/pybind11#4319 (comment) Essentially the behavior of std::type_index is different between the two standard libraries. This behavior seems like a bug in LLVM's implementation and requires us to be careful whenever storing std::type_index in a hashmap when using libc++;
The text was updated successfully, but these errors were encountered:
VoltrexKeyva
changed the title
Differing behavior of std::type_index hash and equality from libc++ and libstdc+++
Differing behavior of std::type_index hash and equality from libc++ and libstdc++
Mar 30, 2023
Why is this considered a bug rather than a permissible implemenation divergence?
I think it's intended that libc++'s type_info can be ABI-compatible with other implemenations, but I'm not sure whether it's a goal for libc++'s type_info::hash_code to have the same results as others.
Oh, libc++'s type_info doesn't seem to handle the leading '*' in the mangled name, which is probably the bug.
Full background can be found on the linked discussion pybind/pybind11#4319 (comment) Essentially the behavior of
std::type_index
is different between the two standard libraries. This behavior seems like a bug in LLVM's implementation and requires us to be careful whenever storingstd::type_index
in a hashmap when using libc++;The text was updated successfully, but these errors were encountered: