AbstractFramebuffer: Fix Android reorder-ctor warning #12099
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
Move declaration of m_additional_color_attachments so its initialization order matches that of the constructor.
iwubcode
approved these changes
Aug 13, 2023
Dentomologist
deleted the
abstractframebuffer_change_member_declaration_order
branch
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.
Move the declaration of m_additional_color_attachments so its initialization order matches that of the constructor.
This was the simplest way to fix the warning, but if someone wants to argue the declaration should be somewhere else I could reorder the constructor initializers instead.