tree f551b9c277ae7d9aa60366d3fec16fbf21f9ba63
parent 9ec75a50bc48c84c68430f113332769d23481ef5
author Michael Buch <michaelbuch12@gmail.com> 1750178247 +0100
committer GitHub <noreply@github.com> 1750178247 +0100
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsFcBAABCAAQBQJoUZnHCRC1aQ7uu5UhlAAA5FMQABOIy7YF3TzxZivkhQW7BexD
 9jX/3CJRoc5CbX2eGZgUIqYWv8kFQZJoq327Y4AuIdT+pSfE6ao4kK/XD+JLZGqA
 7UhsYl7FQcjVoSCnk+mS3p42JTJ6Si701DJVLPLXL0poiEgx3D0SMp20wNgzib0z
 +UUsyuBaL70ua2BJlRqHTcds7rfu1z9e9px5670RPLWF6T1Pfo1iJuYN6IONezW0
 UtifAXh+CoZ7+Nr57ILNyAq4KAlSaI4xORIibWlVTlzLhsXZI3cvnXrnYfWBfd4y
 YwxUSAu5kzUnzVt6vYXejuttrhzYu6CfssR6eHG7jaVichOE3PdTQa154zz3AB67
 JugEE56t0z1iVj/0l8GRYKyZZi/hEJmfxe3z8U2lIvQBGEnHwtxCKrcVG6eBLhMu
 kTQytGwIS3b+TTMjEoqx4n58WelPqrXclg+7AimaS9nMFm662FU/ay+tzVBQTRoY
 TmzZmYhEOiV0HDCJ1O97gJxgAXFc1nvgEP4AjHngVEzqqiop9hrh8zwLGi5OwTUj
 +kXxtWiKkY4v0UTcqOOEVixS4UWcEvNuc6iQPSpGMkHYPIjxF00R3ltCCVqi0KWA
 iQaBMyFtpYghZL8Rd6W1pF3Hxm9G/NPhdzSxWto05CKCvz3NMqDydciEvEiP7f2l
 NwZS8kiBFlYZnYFO9RiG
 =yiFp
 -----END PGP SIGNATURE-----
 

[lldb][Formatter] Get element type for unordered_maps from __hash_table::value_type (#144517)

https://github.com/llvm/llvm-project/pull/143501 changes usage of
`__hash_value_type` in libcxx to an empty tag type. This type will no
longer have a definition in DWARF. Currently the LLDB unordered_map
formatter deduces the map's `element_type` by looking at the `__cc_`
member of `__hash_value_type`. But that will no longer work because we
only have its forward declaration. Since what we're really after is the
type that `__hash_value_type` is wrapping, we can just look at the
`__hash_table::value_type` typedef. With
https://github.com/llvm/llvm-project/pull/143501 that will now point to
the `std::pair` element type (which used to be what we got from
`__cc_`).

TBD: need to double-check this works for older layouts. Quick glance at
the code makes me suspicious of cases like `unordered_map<std::pair<int,
int>, int>`