-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
vk: refactor utils into its own namespace #8280
base: main
Are you sure you want to change the base?
Conversation
We move the code that was contained within two "utils" files into separate utils sources in the vulkan/utils directory.
|
||
namespace filament::backend { | ||
namespace filament::backend::fvkutils { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
why didn't you use utils
? is it because it becomes ambiguous with filament::utils
?
why the f
? what about just vkutils
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The fvk
stands for "Filament Vulkan". I already use FVK_
for various constants to distinguish it from VK_
constants in the vk API. I also didn't want to introduce a filament::backend::utils
since that seems like something that's something shared across backends.
We move the code that was contained within two "utils" files into separate utils sources in the vulkan/utils directory.