You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 23, 2020. It is now read-only.
There are certain mutations whose results I just don't like, even though they lead to code that is equivalent for the cases relevant to my code base. For example, in a case where symbol always has a value that is a symbol, symbol == :foo will get mutated to equivalent eql? and equal?. In many cases, it would be nearly impossible to add a test that makes this mutation go away, and such a test would often be quite convoluted.
Since, functionality being equal for the relevant case, I would rather see the original form in my code base, I'd like to be able to disable these mutations. Ideally, it should be possible to do this both using some configuration file for an entire project, and using comments in the code itself.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
There are certain mutations whose results I just don't like, even though they lead to code that is equivalent for the cases relevant to my code base. For example, in a case where
symbol
always has a value that is a symbol,symbol == :foo
will get mutated to equivalenteql?
andequal?
. In many cases, it would be nearly impossible to add a test that makes this mutation go away, and such a test would often be quite convoluted.Since, functionality being equal for the relevant case, I would rather see the original form in my code base, I'd like to be able to disable these mutations. Ideally, it should be possible to do this both using some configuration file for an entire project, and using comments in the code itself.
The text was updated successfully, but these errors were encountered: