noir-lang / acvm-docs Goto Github PK

Problem

We should explain why we have it/use cases for it.

Proposed solution

See: noir-lang/acvm#191

Alternatives considered

No response

Additional context

No response

Submission Checklist

• Once I hit submit, I will assign this issue to the Project Board with the appropriate tags.

Problem

1. Discuss more the nuances of compiling opcodes like when to use Stop, Return and Foreign Call
2. Discuss in more detail in the example how the foreign call would be handled with the syscall analogy

Happy Case

This explains to a generally technical programmer how to write a compiler that uses these, and how to think of their execution model

Alternatives Considered

Don't document this, they use the code. This is always the fallback plan, but we don't want the code to be the spec.

Additional Context

No response

Would you like to submit a PR for this Issue?

Yes

Support Needs

No response

Problem

We need documentation around what opcodes Brillig will support for advanced developers who want to inspect the Brillig opcode or for those who want to create a frontend which compiles to it.

Proposed solution

See: noir-lang/acvm#227

Alternatives considered

No response

Additional context

No response

Submission Checklist

• Once I hit submit, I will assign this issue to the Project Board with the appropriate tags.