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
Normally the compiler warns the user when they define two enumerations with the same name:
enum test { elem1 }; enum test {}; // warning 201: redefinition of constant/macro (symbol "test1")
But if the first enum is empty, redefinition goes unnoticed:
enum test {}; enum test {}; // No warning(s)
See above.
The text was updated successfully, but these errors were encountered:
Fixed in #577.
Sorry, something went wrong.
No branches or pull requests
Issue description:
Normally the compiler warns the user when they define two enumerations with the same name:
But if the first enum is empty, redefinition goes unnoticed:
Minimal complete verifiable example (MCVE):
See above.
Workspace Information:
The text was updated successfully, but these errors were encountered: