jimingham wrote: Theoretically someone could make a synthetic type or an array with more than UINT32_MAX elements, and with this change we can't support displaying that. I did get one bug report that this didn't work a few years back, though this likely a very uncommon case. If it were easy to go the other way, and pipe num_children as a size_t meaningfully through clang and lldb, that would be formally better. But that's a nice to have, and if the clang changes would be disruptive, then this change is also fine by me. Better to not lie to ourselves about what we can do.
https://github.com/llvm/llvm-project/pull/83501 _______________________________________________ lldb-commits mailing list lldb-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
