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
We just ran into an interesting case, there's code that uses const_get(foo, false). The false prevents lookup in ancestors.
Replacing false with nil also works, but is undocumented. It is less clear, and might break in the future. So leaving the false in we have live mutant.
So, what to do? Would you replace it with nil anyway? Do we need some way to flag that this statement should not be mutated?
The text was updated successfully, but these errors were encountered:
Yes, I would also really like that. I have a different reason for this. When I'm comparing Symbols, I would still like to use #==, even though I could use #equal? (but I can't use #== because I'll still have living mutants).
I like the idea, but I do not have a need to do it for my projects. So tagging as not-on-authors-free-time to encourage funding or (preferred) outside contribution.
We just ran into an interesting case, there's code that uses
const_get(foo, false)
. The false prevents lookup in ancestors.Replacing
false
withnil
also works, but is undocumented. It is less clear, and might break in the future. So leaving the false in we have live mutant.So, what to do? Would you replace it with nil anyway? Do we need some way to flag that this statement should not be mutated?
The text was updated successfully, but these errors were encountered: