rspec/rules/S2159/python/rule.adoc

59 lines
1.4 KiB
Plaintext
Raw Normal View History

== Why is this an issue?
2021-01-27 13:42:22 +01:00
In some cases a comparison with operators ``++==++``, or ``++!=++`` will always return True or always return False. When this happens, the comparison and all its dependent code can simply be removed. This includes:
2020-06-30 12:48:07 +02:00
* comparing unrelated builtin types such as string and integer.
* comparing class instances which do not implement ``++__eq__++`` or ``++__ne__++`` to an object of a different type (builtin or from an unrelated class which also doesn't implement ``++__eq__++`` or ``++__ne__++``).
2020-06-30 12:48:07 +02:00
=== Noncompliant code example
2020-06-30 12:48:07 +02:00
2022-02-04 17:28:24 +01:00
[source,python]
2020-06-30 12:48:07 +02:00
----
foo = 1 == "1" # Noncompliant. Always False.
foo = 1 != "1" # Noncompliant. Always True.
class A:
pass
myvar = A() == 1 # Noncompliant. Always False.
myvar = A() != 1 # Noncompliant. Always True.
----
=== Compliant solution
2020-06-30 12:48:07 +02:00
2022-02-04 17:28:24 +01:00
[source,python]
2020-06-30 12:48:07 +02:00
----
foo = 1 == int("1")
foo = str(1) != "1"
class Eq:
def __eq__(self, other):
return True
myvar = Eq() == 1
myvar = 1 == Eq()
myvar = Eq() != 1 # Ok. "__ne__" calls "__eq__" by default
myvar = 1 != Eq()
----
ifdef::env-github,rspecator-view[]
'''
== Implementation Specification
(visible only on this page)
=== Message
* Remove this equality check between incompatible types X and Y; it will always return True/False
'''
== Comments And Links
(visible only on this page)
include::../comments-and-links.adoc[]
endif::env-github,rspecator-view[]