Skip to content
New issue

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

refactor: convert counter_status enum to enum class #5880

Conversation

bhumitattarde
Copy link
Contributor

Towards #4702

Proposed Changes

  • converted counter_status enum to enum class.
  • added clang's .cache & cmake-tools's cmake-build directory to .gitignore. These are some of the most widely used extensions for C++ development using VSCode.
  • formatted server/papi.cpp (since this file was getting touched as a part of this change).

Any background context you want to provide?

This change can probably be improved by making ostream overload print enum name strings instead of enum int values. Thoughts?

Checklist

Not all points below apply to all pull requests.

  • I have added a new feature and have added tests to go along with it.
  • I have fixed a bug and have added a regression test.
  • I have added a test using random numbers; I have made sure it uses a seed, and that random numbers generated are valid inputs for the tests.

- converted enum counter_status to enum class
- added clang's `.cache` dir to gitignore
- formatted server/papi.cpp
@jenkins-cscs
Copy link
Collaborator

Can one of the admins verify this patch?

@hkaiser
Copy link
Member

hkaiser commented May 2, 2022

@bhumitattarde thanks for this. Unfortunately, this seems to be a duplicate of #5857.

@bhumitattarde
Copy link
Contributor Author

@hkaiser Aah, I did not see that. My apologies. I'll close this PR.

@hkaiser
Copy link
Member

hkaiser commented May 2, 2022

@hkaiser Aah, I did not see that. My apologies. I'll close this PR.

No reason to apologize. We really appreciate your initiative. Let's talk about things before you start working on something to avoid these situations.

@bhumitattarde
Copy link
Contributor Author

@hkaiser Aah, I did not see that. My apologies. I'll close this PR.

No reason to apologize. We really appreciate your initiative. Let's talk about things before you start working on something to avoid these situations.

Thank you. I'll definitely keep that in mind next time. : )

@hkaiser hkaiser added this to the 1.8.0 milestone May 2, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants