Ready for review. @leolara
To run this:
```
pip install jupyter-book
jupyter-book build book # book is the sub-directory where all the book stuffs live in
```
A `_build` folder with `html` artifacts should be created. Terminal
should print out directions on how to open the build files in the
browser. For example, pasting a local directory like
`file:///Users/steve/Documents/repo/chiquito-6_2_23_v10/chiquito/book/_build/html/index.html`
into the browser bar.
Once we are good with the content and merge. I shall create a follow up
PR that add CI to auto builder and host the book via gh-pages, though it
could take quite some tweaking as our gh-pages branch currently builds
and hosts the Rust doc.
CI will follow something like the following:
https://jupyterbook.org/en/stable/start/publish.html
@leolara Ready for review.
All MiMC7 notebook files are `part4` of the tutorial, with 4 chapters,
the first 3 of which is fully written out (just because they sort of
came out naturally rather than to an outline first, so I thought this
actually saved more time), and the last of which is an actual outline
with `// TODOs`.
Let me know your thoughts!
Will be PR'ed to main.
@leolara Ready for review and the MiMC7 example is fully functional.
# My technical approach
- Pass over JSON of sub-circuit AST to Rust. Obtain uuid.
- Pass over JSON of sub-circuit TraceWitness to Rust using the same
uuid.
- `halo2_mock_prover` function takes vector of uuids and compiles super
circuit before passing it to the mock prover.
