-
-
Notifications
You must be signed in to change notification settings - Fork 2.9k
Consider adding --strict-equality to --strict #7910
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
I don't know what you are doing, everything works perfectly for me. Maybe you have have a broken install, or something else. |
I was using |
Hm, actually now that it is a bit more "mature" we can make it a strict flag, unless @msullivan is against. See also #7469 |
Fine by me. |
JukkaL
added a commit
that referenced
this issue
Jan 16, 2020
JukkaL
added a commit
that referenced
this issue
Jan 16, 2020
Fixes #7910. The stub changes are needed for clean output when using --strict.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This doesn't report any errors with
--strict-equality
:even though the third example is from the docs.
Versions:
The text was updated successfully, but these errors were encountered: