Daniel Gollahon

I think there is another report option for use in CI contexts that doesn't overwrite the screen. I don't recall the flag off the top of my head though.

Could you share the corresponding source you are testing? As well as the full `mutest` command you are using? Also, I assume these errors don't happen when you're just running...

Ah, so `mutest` is not refinements-aware. The reason you don't see any mutations in `array_utility` is because those are the only methods defined. In `String-Utility-Ruby` the mutations you're seeing are...

Right. That's what i meant about > where you're just being defensive / conservative (which is probably ok). which is an argument for special casing it. OTOH if we wanted...

note: We also want this to work for multi-assignment (`a, = *b` -> `a, = b`)

@mvz: Yeah, I agree. I've been wanting that myself for a while. There's definitely work to be done on the reporter.

There are issues--the naive forwarding breaks in some cases. Here is an [example from `mutant`](https://github.com/mbj/mutant/commit/d146f957a9316c826c6e846c24ae82a698648a32#diff-68198e1d68f5364ace6fdb3be566c8f96d56b54dc92939fbfb53ad242ca533a1R3-R19). This applies to at least shared_examples, but maybe niche uses of other constructs as well....

> Today, I used rspectre to remove 250 unused lines from our spec suite. So: Thank you! Awesome! Glad it was helpful. :D > Would it be possible for rspectre...

I think this is now roughly three categories of features I want: - Remove unused doubled methods from `spy`, `instance_spy`, `double`, `instance_double`, `object_double`, etc. - Remove unused stubs from `expect`,...

> Remove unused stubs from expect, allow, receive_message_chain, etc. This issue now just tracks this--I split out the other two.