Mathieu Barbin

I've noticed similar issues reported in #418 and #432, which I believe might be related. In my experience, when running tests instrumented with `bisect_ppx`, if the `BISECT_FILE` environment variable is...

Thank you, @mooreryan. Your response was enlightening! It has motivated me to delve deeper into bisect_ppx, and I've enabled it in several more repositories. I believe your explanation about the...

I have a hunch about issue `2`: It seems that my server is being signaled to quit and exits before it has a chance to write the coverage data. I'll...

@liweijian I may have a related issue. Would you mind having a look at #411 and let me know if `BISECT_FILE` does anything for you? I'm preparing to use `bisect_ppx`...

Thanks @jmid for your review! Looking back, I'm not sure why I left the `deriving_inline` construct here. I used it to track generated code while working on the PR, but...

`Finally, for symmetry I would have liked to see QCheck(1) support too, but I think this is too much to require. If you can get QCheck2 to work, I may...

Hello, I wanted to provide an update regarding supporting the [@@deriving qcheck2] construct in signatures. After further consideration and exploration of my project requirements, I've decided to take a different...

Thank you for taking the time to review the PR and for your comments! I really appreciate your detailed feedback and am working on responding to each of your points...

> I would suggest to keep the tests that are redundant right now locally, and to include them as part of the PR if you do suggest an alternative instrumentation...

Thank you for the explanation. I now understand how post-instrumentation contributes to coverage checking when the returned value of an apply is embedded in larger expressions, such as record or...