Fork me on GitHub
#parinfer
<
2018-02-06
>
cfleming03:02:13

@shaunlebron I finally sat down to try to create some test cases, and the ones I’ve tried so far actually work fine in parinfer JS, so some of them at least are bugs I’ve introduced while porting.

cfleming03:02:23

I have some more cases, I’ll continue testing.

cfleming03:02:28

Ok, I believe that all these cases I’ve accumulated work in parinfer JS, and I have a bug introduced when porting. They actually all look fairly similar when reduced, hopefully they’re all just a single bug.

shaunlebron03:02:59

@cfleming: awesome, glad to hear it!

cfleming03:02:11

Now I just have to find it 😞

cfleming03:02:58

I’m actually considering instrumenting parinfer to print constraints after each char, so that I can compare the two in cases like this.

cfleming03:02:09

Otherwise I just spend a ton of time in the debugger.