You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
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.
The text was updated successfully, but these errors were encountered: