generator: Use PFN_ types for struct members instead of repeating signature
#438
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
force-pushed
the
use-pfn-in-struct
branch
3 times, most recently
from
da5cdc9
to
ee44930
Compare
MaikKlein
approved these changes
May 23, 2021
Following the fixes in #437 this actually puts those function pointer typedefs to use, slimming down the code by a large margin at the same time.
MarijnS95
force-pushed
the
use-pfn-in-struct
branch
from
0d0d221
to
ef993e3
Compare
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.
Depends on #439, #436, #437
Following the fixes in #437 this actually puts those function pointer typedefs to use, slimming down the code by a large margin at the same time.