Tracking Issue for `debugger_visualizer`

[wesleywiser]

This is a tracking issue for RFC 3191.
The feature gate for the issue is #![feature(debugger_visualizer)].

About tracking issues

Tracking issues are used to record the overall progress of implementation.
They are also used as hubs connecting to other relevant issues, e.g., bugs or open design questions.
A tracking issue is however not meant for large scale discussion, questions, or bug reports about a feature.
Instead, open a dedicated issue for the specific matter and add the relevant feature gate label.

Steps

• Implement the RFC
• Adjust documentation (Add documentation for debugger_visualizer attribute reference#1335)
• Stabilization PR (Stabilize debugger_visualizer #108668)

Unresolved Questions

No unresolved questions at this time.

Implementation history

• Create new attribute #[debugger_viusalizer] and add support for embedding NatVis visualizers through this attribute: Add a new Rust attribute to support embedding debugger visualizers #91779

• Adding support for embedding pretty-printers via new attribute: Add support for embedding pretty printers via #[debugger_visualizer] attribute #97028

[ridwanabdillahi]

@rustbot claim

[ridwanabdillahi]

Implementation History

• Create new attribute #[debugger_viusalizer] and add support for embedding NatVis visualizers through this attribute: Add a new Rust attribute to support embedding debugger visualizers #91779

• Adding support for embedding pretty-printers via new attribute: Add support for embedding pretty printers via #[debugger_visualizer] attribute #97028

[madsmtm]

What's the plan for LLDB? It seems like the design of LLDB is slightly different, they err on the side of "the binary cannot be trusted", so automatically loading these kind of things is not really supported - but maybe it would be possible to provide when using rust-lldb?

[pravic]

Why

#![debugger_visualizer(natvis_file = "../Foo.natvis")] 

in Rust code and not

debug_visualizer = "foo.natvis"

in Cargo.toml?