Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Provide separate example code for C and C++ bindings #50

Open
jherico opened this issue Oct 4, 2024 · 1 comment
Open

Provide separate example code for C and C++ bindings #50

jherico opened this issue Oct 4, 2024 · 1 comment
Labels
enhancement New feature or request

Comments

@jherico
Copy link

jherico commented Oct 4, 2024

The example code for the Vulkan API on the docs site uses the C bindings pretty much exclusively, but virtually all the surrounding code is written in C++. This results in downstream users virtually always using the C bindings, even if they're writing in a C++ context.

Modern documentation sites for cross-language libraries, like the AWS CDK library, often provide examples in multiple language. I would suggest that the tutorials be expanded and updated to include fully C examples that exclusively use the C bindings and fully C++ examples that exclusively use the C++ bindings. Without setting this kind of precedent, the C++ bindings and their improved type safety and other advantages will remain underutilized.

@SaschaWillems
Copy link
Collaborator

SaschaWillems commented Oct 5, 2024

That is something we are considering for the whole documentation site, but not with high priority right now. There are other pressing issues with the tutorial that need fixing first.

For people wanting to see how to use the C++ bindings, we have lots of Vulkan.hpp samples at https://github.com/KhronosGroup/Vulkan-Samples

@SaschaWillems SaschaWillems added the enhancement New feature or request label Oct 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants