Visual Studio debugger support
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 45/100
Research direction
Start by reviewing the attached Variant.natvis and InstallVSDebuggerVariantSupport.bat files, along with the repository's existing project layout and contribution guidance. Confirm how Visual Studio Native Visualizer files are expected to be included, then verify that variant values can be inspected in the debugger for the supported types; done means the support is available through the project or documented installation path.
Written by the indexing model from the issue text.
Description
I created a Visual Studio Native Visualizer file for variant.
This file enable the debugger to view the value in a variant variable.
There are two files here:
- Variant.natvis - the XML describe how to view the variant in VS debugger
- InstallVSDebuggerVariantSupport.bat - simple batch file to copy the nativs file to VS debugger folder
- One can also just add it to the project itself, the debugger will peek it up from there.
The natvis file support up to 20 types, if you think we need to support more, tell me and I will upload a new file.
VS Natvis format requires to explicitly describe each variant (with 1, 2, 3... types).
I use the boost::variant nativs file as a reference, and there it describe up to 20.
Enjoy :-)
- Dominant language
- C++
- Stars
- 385
- Forks
- 96
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing 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.
More from mapbox/variant
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
-
Difficulty 3/5 1-2 days Newbie friendliness 25/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 25/100
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
-
Possible data corruption when assigning variant to itselfMay be free again @artemp claimed this 3186 days ago, and no pull request is open. Open
Similar issues
-
bug chart-audit
Difficulty 1/5 Under an hour Newbie friendliness 92/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
godotengine/godot#124120 ·
Maintainers usually reply within 1 day
-
HasBacktrace Priority-Critical
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
azerothcore/azerothcore-wotlk#27921 ·
Maintainers usually reply within 1 day
-
area/ysql kind/bug priority/medium
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
yugabyte/yugabyte-db#34584 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
Maintainers usually reply within 1 day