Sage Mitchell

The README points to `tests/lib.rs` which has a couple useful examples. I don't see any context like that in the docs, though.

I'm seeing behavior in `cargo-watch` and `watchexec` which might be explained by this bug and, if it's related, a potential clue. * Windows 10 Pro * WSL2 with Ubuntu 20.04...

Is there a target version for this fix? I was surprised to see unhandled cases, in addition to unproductive self-reference, aren't checked. For example, ``` total vadd : Num a...

Should this be closed?

Thanks for the leads. Sam offered some tips too. It occurred to me I hadn't tried simplifying the `struct` more. Interestingly, the unexpected behavior _disappears_ with this change. ```diff @@...

Found some more clues with the help of `cargo nexus run`'s `-v` option. Outputs below have been piped through `cat -n | awk 'length($2) > 7' | grep ecall`, so...

I made some minor changes to the program in 0e1a90d6 to facilitate debugging, like adding more `print!` calls and prefixing+suffixing all outputs with `~~`. I also added some `tracing::trace!` calls...

The proposed `Prover` trait and the sample interface code are both helping me get a taste of where we are and potential directions we can go. Highlighting a couple points...

I broadly agree with @slumber's feedback. Here are some additional thoughts: 1. Consider having `Engine::load` take a `P: AsRef` instead of a `&PathBuf`. This more flexible and align with [`std`...

>> Is Engine::enable_prover_mode needed when there's both Engine::execute and Engine::prove? > I debated this. The flow I was concerned with enabling looks like: > > ```rust > let engine =...