Skip to content

introducing LIBASSERT_WARNING_PRAGMA_PUSH_MSVC/LIBASSERT_WARNING_PRAGMA_POP_MSVC #135

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

Open
wants to merge 1 commit into
base: dev
Choose a base branch
from

Conversation

GerHobbelt
Copy link

introducing LIBASSERT_WARNING_PRAGMA_PUSH_MSVC/LIBASSERT_WARNING_PRAGMA_POP_MSVC, analogous to the GCC and CLANG ones. This is used in the LIBASSERT_INVOKE macro and a few other spots to help supress compiler warnings. (LIBASSERT_IGNORE_UNUSED_VALUE)

…MA_POP_MSVC, analogous to the GCC and CLANG ones. This is used in the LIBASSERT_INVOKE macro and a few other spots to help supress compiler warnings. (LIBASSERT_IGNORE_UNUSED_VALUE)
Copy link
Owner

@jeremy-rifkin jeremy-rifkin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for taking the time to do this, what causes msvc to emit an unused value warning here?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants