Simplify triangle example's vertex input state #512
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
MarijnS95
approved these changes
Dec 19, 2021
There was a problem hiding this comment.
Nice catch! I'm quite surprised though why the original commit, that said "to use builders and defaults", removed this exact use of the builder pattern to substitute it with that manual assignment... 0a16b5b#diff-99480e84b5476c223fd790be90ef853c9f4295d15113172f83679b2882ece4e6L259-R278
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Use a
PipelineVertexInputStateCreateInfobuilder to pass a slice instead of a pointer and length. Also makes the triangle example a little more consistent with the texture example.