Fix inconsistent management of ExtSuffix in INIT macros #453
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.
Proper handling of ExtSuffix was missing from in #422 (could be listed in the followup issue #427).
Note that this does not account for potential
namespace
, because I am not sure how we should handle it: if a member from a structfoo
has type tostruct.bar
, can we be sure that there is a singlebar
entry and use its namespace, or should we look forbar
first in the same namespace asfoo
, then fallback to default namespace?SIde note: neither ExtSuffix not namespaces are tested, we could have a minimal extension example in
test
.