Markus Schirp

@dgollahon I think that these are not an issue anymore with #1361, right?

@dgollahon I just tested all of this examples they produce good mutations since 0.11.18. Since we do not have mutations specific to this AST structures I'm closing this without porting...

@vaporyhumo This is now supported via ignore patterns: ``` mutation: ignore_patterns: - 'send{receiver=const{name=T}}' ```

@devinburnette Overall: Yes, in detail: We should not replicate rubocop todo file semantics as these assume you can do a pass over the entire code base in a reasonable time...

I'm happy to support a mode where mutant generates an ignore list, if we put a warning in about the runtime of that generator. But: I wounder if we can...

AFAIK it originates from: * `Proc` * And a general "superhero movie scheme" we used for lots of datamapper 2.0 support gems. Materials, imaginary hero names themselve etc: Siblings are:...

OT: If you like procto check these out.

There is also [mutant](https://github.com/mbj/mutant)

> Please use permalinks in issue reports; as you can see, your link is already shifted. sorry, oversight on my side.

Yeah, so overall there is no validation of the content of the stack binary being done. Which is standard practice for any download in the space. Stack by itself validates...