Maxim Vezenov

After an internal meeting and the complexity introduced in https://github.com/noir-lang/noir/pull/3979 we have decied to temporarily shelve nested slices. In the main issue a new tracklist has been created to mark...

I will leave https://github.com/noir-lang/noir/issues/528 to be closed once this issue is closed.

Closing this issue now that all tasks have been completed. Any new slice bugs can be separate from this issue.

Going to close this issue now that https://github.com/noir-lang/noir/pull/5155 is merged.

We could have that a circuit marked with #[recursive] attribute automatically spits out a proof and vkey in the format that the backend expects for recursive proofs. This may have...

> If this is relatively easy to do with barretenberg, shall we get this in to resolve this Issue and improve devs' lives first and spin up another Issue for...

> Could we not have `nargo prove` spits out both: Yeah that could be a good compromise. A backend could just deal with multiple proof and/or vkey formats. I would...

> nargo prove --recursive-artifacts This type of flag is what we would like to avoid. It is why we moved away from a `is-recursive` flag to putting an attribute on...

> Main trouble I'm running into is that we're storing a proof with public inputs stripped off in the `proofs` directory whereas `bb` expects to have the correct number of...

Is this issue related (https://github.com/noir-lang/noir/issues/2540)? @michaeljklein Could you check if it is resolved by your work?