[FEATURE] Difficult to understand C++ RAII syntax in tutorial
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 20/100
- Issue type
- Documentation
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- cpp
- Domain
- documentation
Research direction
Review the tutorial context for the C++ RAII syntax concern and inspect linked pull request #202 before doing any work. Done would mean that the tutorial's RAII explanation is clearer, but the issue does not specify the affected page, files, tests, or exact wording.
Written by the indexing model from the issue text.
Description
Does the feature request belong in this repository?
If you have a request regarding the structure and content of a particular component of docs.vulkan.org, please file that request in the repository corresponding to the component the request would affect:
- For the Vulkan Specification, Features, and Reference Pages components: Use the Vulkan-Docs repository
- For the OpenGL Shading Language Specification and GLSL Extensions components: Use the GLSL repository
- For the Khronos Vulkan Tutorial component: Use the Vulkan-Tutorial repository
- For the Vulkan Guide component: Use the Vulkan-Guide repository
- For the Vulkan Samples component: Use the Vulkan-Samples repository
- For problems with docs.vulkan.org navigation, style, search, and overall site structure, file an issue here
Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.
- Dominant language
- C++
- Stars
- 424
- Forks
- 127
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 7
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.
More from KhronosGroup/Vulkan-Tutorial
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
KhronosGroup/Vulkan-Tutorial#519 · 1 assignee ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
KhronosGroup/Vulkan-Tutorial#508 · 1 assignee ·
-
Difficulty 1/5 Under an hour Newbie friendliness 74/100
KhronosGroup/Vulkan-Tutorial#499 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
KhronosGroup/Vulkan-Tutorial#498 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
KhronosGroup/Vulkan-Tutorial#497 ·
All issues in KhronosGroup/Vulkan-Tutorial
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
google/libultrahdr#485 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
godotengine/godot#123776 ·
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 60/100
-
good first issue
Difficulty 1/5 Under an hour Newbie friendliness 90/100
-
good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
ros2/common_interfaces#344 ·