Markus Schirp
Markus Schirp
This is far from beeing pointless. `return sql` to `sql` is a valid mutation. In this case it does not change the behavior of the code, as it is the...
It is valid ruby code. ``` ruby def foo(arg) if arg == 1 return 2 end 3 end ``` Will be mutated to: ``` ruby def foo(arg) if arg ==...
I'll track this issue as enhancement. (The enhancement is the addition of the option to skip this specific mutation).
@postmodern I just added the basic infrastructure to inject configuration into the mutators. See fc426bee869291af0c4e8472227ef85aed129c96. I think I can fix this issue soon. I dunno how the CLI should look...
I personally think that adding CLI switches is not an option since this case is too specific. It'll be handled via the upcoming config file support.
I think that I'll never to this. Its a feature I'll _never_ use by myself. And maintaining features I do not use is a bad idea. My OSS time is...
Reopening it, but tagging on `not-on-maintainers-time`. Its a nice idea, that might help others. So worth keeping in the tracker. But I can only support this in the following cases:...
Now as mutant is commercial, I'm planning to allow configuration of this nuance.
> @tjchambers Would it have helped if expressions that are just syntactic sugar were expanded first, then mutated: @dkubb JFYI: `a ||= b` is NOT syntactic sugar for `a =...
BTW Above inorthogonality is the reason rubies parser has separate nodes for all op assigns.