We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
ParseCallbacks::item_name
enum long_prefix_to_remove_foo { BAR = 0 }; int long_prefix_to_remove_bar();
There is no way to implement ParseCallbacks::item_name that can follow different naming logic for these two items.
I propose that item_name be refactored to look more like generated_name_override, which passes in an info struct instead of solely a name.
item_name
generated_name_override
Cc @vsukhoml
The text was updated successfully, but these errors were encountered:
Seems sensible.
Sorry, something went wrong.
Successfully merging a pull request may close this issue.
Input C/C++ Header
There is no way to implement
ParseCallbacks::item_name
that can follow different naming logic for these two items.I propose that
item_name
be refactored to look more likegenerated_name_override
, which passes in an info struct instead of solely a name.Cc @vsukhoml
The text was updated successfully, but these errors were encountered: