01:13 <dkubb> memos

01:13 <Cinchy> dkubb: [3h 4m 17s ago] <mbj> mutant-0.3.beta1 is on github

01:13 <Cinchy> dkubb: [3h 3m 49s ago] <mbj> s/github/rubygem/

01:15 <mbj> .

01:53 <dkubb> !memo mbj can mutant run mutations in parallel and then aggregate the results and display them serially like parallel_tests does?

01:53 <Cinchy> dkubb: Memo recorded for mbj.

01:53 <dkubb> !memo mbj er, not can.. obviously it doesn't do it now. I mean, do you think that's something that can be accomplished with the way mutant works?

01:53 <Cinchy> dkubb: Memo recorded for mbj.

06:32 <dkubb> !memo mbj I wonder if it would be possible to make a double lib like rspec-fire, except have it only allow you to mock behaviour specified in the YARD doc contract. this may be a step above the recent batch of double libs that try to be like rspec-fire

06:32 <Cinchy> dkubb: Memo recorded for mbj.

08:52 <dkubb> !memo solnic I just pushed the most basic thing that could work wrt an in-memory adapter. it only supports base relations atm. I'm going to build a gateway on top of this so at least there's something to test against in ROM. once I get that working I'll start figuring out how to unwind the relations and write to the appropriate base relations

08:52 <Cinchy> dkubb: Memo recorded for solnic.

08:59 <solnic> .

08:59 <Cinchy> solnic: [6m 40s ago] <dkubb> I just pushed the most basic thing that could work wrt an in-memory adapter. it only supports base relations atm. I'm going to build a gateway on top of this so at least there's something to test against in ROM. once I get that working I'll start figuring out how to unwind the relations and write to the appropriate base relations

11:41 <mbj> .

11:41 <Cinchy> mbj: [9h 48m 13s ago] <dkubb> can mutant run mutations in parallel and then aggregate the results and display them serially like parallel_tests does?

11:41 <Cinchy> mbj: [5h 9m 5s ago] <dkubb> I wonder if it would be possible to make a double lib like rspec-fire, except have it only allow you to mock behaviour specified in the YARD doc contract. this may be a step above the recent batch of double libs that try to be like rspec-fire

11:41 <Cinchy> mbj: [9h 47m 34s ago] <dkubb> er, not can.. obviously it doesn't do it now. I mean, do you think that's something that can be accomplished with the way mutant works?

11:42 <mbj> dkubb: Yeah it is possible, I'll create a parallel killer soon.

11:42 <mbj> The runner infrastructure is decoupled enough to allow such changes!

20:01 <dkubb> !memo solnic how do you like bogus? I've been thinking about using something similar to it, rspec-fire or ducky. I just wish that there was one that parsed YARD docs and used that in addition to source code to setup expectations.. I think there's enough info in a YARD doc to augment the constraints

20:01 <Cinchy> dkubb: Memo recorded for solnic.

21:24 <dkubb> !memo mbj what if the no-op step is clobbering the visibility of the method? I noticed the source_location seems to be change by about 3 lines between the original and when mutant sees it?

21:24 <Cinchy> dkubb: Memo recorded for mbj.

22:02 <dkubb> !memo mbj yay, with those two proposed fixed to mutant axiom-types now passes with mutant again, at 100% coverage

22:02 <Cinchy> dkubb: Memo recorded for mbj.