Rollup merge of #164975 - Walnut356:unsized_vis, r=davidtwco

Add wide pointer visualizer for LLDB

This visualizer handles wide pointers to `?Sized` types, e.g.

```
struct S {
    a: u8,
    b: [i16]
}
```

These were undecidable not too long ago, but we [now have enough information to reliably visualize these properly](https://github.com/rust-lang/rust/pull/153238).

lldb 23 added the ability for an `SBValue` object to acquire its parent, which is very helpful for this so we can retrieve the length. Prior to lldb 22, the best option we have is to store a reference to the parent wide pointer within python itself and retrieve them in the child's visualizer (this happens via `WidePtrSyntheticProvider.WIDE_PTR_BY_UNSIZED_CHILD_ID`. I know it's maybe a bit hack-y, but this is semi-canonical and CodeLLDB did it pretty extensively in their visualizers). Using that method, we are thankfully able to get identical output between lldb 22 and 23.

As a note, this visualizer *does not* work for MSVC at the moment because [LLDB pretends zero-sized fields in PDB debug info don't exist](https://github.com/llvm/llvm-project/issues/235686) =)
tree: 535b05b026a6c8476535517318848071f2ed980f
  1. .github/
  2. compiler/
  3. library/
  4. LICENSES/
  5. src/
  6. tests/
  7. .clang-format
  8. .editorconfig
  9. .git-blame-ignore-revs
  10. .gitattributes
  11. .gitignore
  12. .gitmodules
  13. .ignore
  14. .mailmap
  15. AGENTS.md
  16. bootstrap.example.toml
  17. Cargo.lock
  18. Cargo.toml
  19. CODE_OF_CONDUCT.md
  20. configure
  21. CONTRIBUTING.md
  22. COPYRIGHT
  23. INSTALL.md
  24. LICENSE-APACHE
  25. license-metadata.json
  26. LICENSE-MIT
  27. package.json
  28. README.md
  29. RELEASES.md
  30. REUSE.toml
  31. rust-bors.toml
  32. rustfmt.toml
  33. triagebot.toml
  34. typos.toml
  35. x
  36. x.ps1
  37. x.py
  38. yarn.lock
README.md

Website | Getting started | Learn | Documentation | Contributing

This is the main source code repository for Rust. It contains the compiler, standard library, and documentation.

Why Rust?

  • Performance: Fast and memory-efficient, suitable for critical services, embedded devices, and easily integrated with other languages.

  • Reliability: Our rich type system and ownership model ensure memory and thread safety, reducing bugs at compile-time.

  • Productivity: Comprehensive documentation, a compiler committed to providing great diagnostics, and advanced tooling including package manager and build tool (Cargo), auto-formatter (rustfmt), linter (Clippy) and editor support (rust-analyzer).

Quick Start

Read “Installation” from The Book.

Installing from Source

If you really want to install from source (though this is not recommended), see INSTALL.md.

Getting Help

See https://www.rust-lang.org/community for a list of chat platforms and forums.

Contributing

See CONTRIBUTING.md.

For a detailed explanation of the compiler's architecture and how to begin contributing, see the rustc-dev-guide.

License

Rust is primarily distributed under the terms of both the MIT license and the Apache License (Version 2.0), with portions covered by various BSD-like licenses.

See LICENSE-APACHE, LICENSE-MIT, and COPYRIGHT for details.

Trademark

The Rust Foundation owns and protects the Rust and Cargo trademarks and logos (the “Rust Trademarks”).

If you want to use these names or brands, please read the Rust language trademark policy.

Third-party logos may be subject to third-party copyrights and trademarks. See Licenses for details.