KhronosGroup / KhronosGroup/Vulkan-Tutorial
[FEATURE] Difficult to understand C++ RAII syntax in tutorial
- Dominant language
- C++
- Stars
- 418
- Forks
- 126
- Avg merge
- 11d 6h
- Merged PRs (30d)
- 31
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](https://github.com/KhronosGroup/Vulkan-Docs/issues/new) repository
* For the OpenGL Shading Language Specification and GLSL Extensions components: Use the [GLSL](https://github.com/KhronosGroup/GLSL/issues/new) repository
* For the Khronos Vulkan Tutorial component: Use the [Vulkan-Tutorial](https://github.com/KhronosGroup/Vulkan-Tutorial/issues/new) repository
* For the Vulkan Guide component: Use the [Vulkan-Guide](https://github.com/KhronosGroup/Vulkan-Guide/issues/new) repository
* For the Vulkan Samples component: Use the [Vulkan-Samples](https://github.com/KhronosGroup/Vulkan-Samples/issues/new) 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.
Contributor guide
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.
Assessment
- Tech stack
- cpp
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100