Jannis Harder

It might be clear from the context, but to avoid confusion, I'd like to clarify that my conflict analysis isn't more efficient compared to other solvers. Adding propagated unit clauses...

I was also getting the `No coverage data found` error, and it seems that the binary compiled with fuzzing instrumentation is at a different path from the main fuzzing binary...

I have another use case for this, which AFAICT was not mentioned so far. When adding a paper via the browser extension, zotero often automatically downloads the corresponding arxiv preprint...

I didn't realize I forgot to add tags, thanks for letting me know. I'll add them with the next release.

Eventually I want to support setting an arbitrary termination callback, i.e. an equivalent of the [`ipasir_set_terminate`](https://github.com/biotomas/ipasir/blob/a09fe113b64c61fb8ed95b19b007d7043540243e/ipasir.h#L151) function of the IPASIR C API. On top of that it would be possible...

I do :) it's not a high priority for me right now, but I will add it eventually. My plan is to have a varisat_ipasir crate that is a wrapper...

Internally, like many solvers, it uses the number of conflicts (how often the search had to backtrack) for this. It is used to schedule restarts and reduction of learned clauses....

I don't have any good advice regarding tool compatibility, I've also never used Jasper. I can confirm that using labels to identify properties seems what most FV users I've interacted...