Markus Schirp
Markus Schirp
> @mbj so it's more like: > > foo || (foo = bar) Yes.
Detecting the presence of `zsuper` in the body is easy. I support this change.
@dgollahon You can use the `parent_node` method to peek up and into a sibling. But this is discouraged and a method of last resort. For now this may be the...
@kbrock The simplecov output is made for line based coverage tools, it does not feature the amount of granularity mutant supports. Both for actual coverage and metadata. I see myself...
> I'll say this again, take a look at CodeClimate's format. The spec describes column/offset and length. Their issue construct seems to fit mutant's use cases. I never voted against...
> Is the goal to produce a log file that other systems can use out of the box? > Or is the thought that the log will be internally focused,...
@mknapik This project has no roadmap, and is only driven by my private interest (that is not focused on ruby recently) or commercial needs. I'm open to accept contributions, and...
The work @mknapik and @joneshf plan to do intersects only slightly but touches the same subsystem `Mutnat::Result*` as input. Hence I think there is some chance for me only having...
@nepalez I like the concept of the gem. But I do not use it in a commercial environment. So I cannot support this on my OSS time. This gem "likely"...
@nepalez For reference this is the current custom injection behavior for adamantium memoizers: https://github.com/mbj/mutant/blob/802e52338f5d6e2954a224e6f375a04c75527426/lib/mutant/subject/method/instance.rb#L30-L56