We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
With @asuessenbach working hard on unifying the framework I was wondering if we could agree on some naming schema for the different binding types.
Using types aliases already makes things a lot easier to read like this:
// Usings using BufferAllocationC = BufferAllocation<vkb::BindingType::C>; using BufferAllocationCpp = BufferAllocation<vkb::BindingType::Cpp>; // Usage vkb::BufferAllocationC do_something(); vkb::BufferAllocationCpp do_something();
Maybe we can improve upon this a little bit by having the C-Binding be the default, and the only suffixing the C++ one?
Like this:
// Usings using BufferAllocation = BufferAllocation<vkb::BindingType::C>; using BufferAllocationCpp = BufferAllocation<vkb::BindingType::Cpp>; // Usage vkb::BufferAllocation do_something(); vkb::BufferAllocationCpp do_something();
Just some food for thought and maybe something we can discuss on the next call.
The text was updated successfully, but these errors were encountered:
Agreed, this would make it more readable
Sorry, something went wrong.
No problem, if the consensus is to use that naming scheme, I can adjust #1085 accordingly.
No branches or pull requests
With @asuessenbach working hard on unifying the framework I was wondering if we could agree on some naming schema for the different binding types.
Using types aliases already makes things a lot easier to read like this:
Maybe we can improve upon this a little bit by having the C-Binding be the default, and the only suffixing the C++ one?
Like this:
Just some food for thought and maybe something we can discuss on the next call.
The text was updated successfully, but these errors were encountered: