-
Notifications
You must be signed in to change notification settings - Fork 10.3k
[FR]: Add EXPECT_DOUBLE_NE and ASSERT_DOUBLE_NE #4612
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
Comments
Hi! If this feature hasn't been taken by anyone yet I'd like to work on it! |
Hi! Looks like a PR hasn't been created yet. @jordans6 are you still working on this? If not, I would like to work on this feature. |
Any updates on this? |
@oToToT I made the changes to my fork and created a PR back in November 2024, however no one has looked at it. For convenience, here is the fork https://github.com/daniel10015/googletest/tree/main and the PR #4670 |
Hi @derekmauro Sorry for directly pinging you here. I'm not the issue owner nor the PR submitter. Further, I'm not sure if you're the right person to ask. Nonetheless, I think having a counterpart to I would like to know if it is possible for you to help review this PR or find the right person to help with this. Please let me (us) know if there is anything wrong about this contribution or the way it was contributed. Thanks in advance. |
Does the feature exist in the most recent commit?
NOPE
Why do we need this feature?
Checking that two doubles are NOT equal is more difficult than it is to check they are equal per S.O.
One approach is to bring in gmock and link to it if you want to check a double value is not equal:
Describe the proposal.
Here is what I would prefer for the API, which use "NE" like
EXPECT_NE
Same with
Is the feature specific to an operating system, compiler, or build system version?
It could be implemented on any OS.
The text was updated successfully, but these errors were encountered: