Skip to content

Fixed code style consistency more #35

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

Merged
merged 2 commits into from
Sep 4, 2017

Conversation

sjfricke
Copy link
Contributor

@sjfricke sjfricke commented Sep 2, 2017

As someone who has looked and used all these tutorials, I noticed a small trend of deviation from the consistent styling from the first few tutorials. Since this might be someone else first time learning how to write android Vulkan code I feel a consistency styling makes the code more readable.

Ran all tutorials to confirm still build and run

As someone who has looked and used all these tutorials I noticed a small trend of deviation from the consistent styling from the first few tutorials. Since this might be someone else first time learning how to write android vulkan code I feel a consistence styling makes the code more readable
@@ -207,6 +207,17 @@ void CreateSwapChain() {
LOGI("<-createSwapChain");
}

void DeleteSwapChain(void) {
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The DeleteSwapChain under the CreateSwapChain as all the other "Create..." have the "Delete..." under it

@@ -64,14 +64,14 @@ struct VulkanSwapchainInfo {
VulkanSwapchainInfo swapchain;

struct VulkanBufferInfo {
VkBuffer vertexBuf;
VkBuffer vertexBuf_;
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

keeping the idea of these Vulkan struct groups ending with an underscore

@ggfan
Copy link
Contributor

ggfan commented Sep 3, 2017

LGTM. could you save your code locally, then try with clang-format -i -style Google, compare your changes against clang-format changes? so we get idea how different it is ( this code here was not run with clang-formt at the beginning though, so I am leaning toward to merge your change ). Thanks

@sjfricke
Copy link
Contributor Author

sjfricke commented Sep 3, 2017

Wow, I can't believe I didn't know about clang-format, that gonna save me so much time in my life in the future

@ggfan
Copy link
Contributor

ggfan commented Sep 4, 2017

thanks for PR. merging!

@ggfan ggfan merged commit 7d70655 into googlesamples:master Sep 4, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants