STL: Verify vNext visualizers
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 11.1k
- Forks
- 1.7k
- Avg merge
- 4d 15h
- Merged PRs (30d)
- 22
Description
As we work on the vNext binary-incompatible branch, we're going to overhaul many STL data structures, often completely breaking their visualizers. Before releasing vNext, we need to audit every visualizer in stl.natvis and add a vNext version if necessary. (We shouldn't change or remove existing visualizers, because stl.natvis supports visualizing previous versions of the STL, and the VS 2019 compatible release series will remain important for some time.)
Also tracked by Microsoft-internal VSO-210364 / AB#210364.
vNext note: Resolving this issue will require breaking binary compatibility. We won't be able to accept pull requests for this issue until the vNext branch is available. See #169 for more information.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Wait for the vNext branch to become available, then audit every visualizer in stl.natvis against the vNext STL data structures. Read the vNext note and #169 first; done means vNext visualizers are added where necessary without changing or removing visualizers for previous STL versions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- devtools
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100