You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The avm bytecode is generated by running ./transpile <input> <output> for each noir output artifact.
If we were to ship this approach to developers once the AVM becomes inshrined within the protocol, we would be required to also ship a complication aztec-nargo build script that ran the transpiler aswell.
I do not think we want to do this, but instead we should have something that is integrated with noir's current aztec-macros abstraction leak.
Overview
With / assuming the completion of #4227
The avm bytecode is generated by running
./transpile <input> <output>
for each noir output artifact.If we were to ship this approach to developers once the AVM becomes inshrined within the protocol, we would be required to also ship a complication
aztec-nargo
build script that ran the transpiler aswell.I do not think we want to do this, but instead we should have something that is integrated with noir's current aztec-macros abstraction leak.
Where does the code go?
Aztec noir's macros currently only perform preprocessing, but to perform transpilation from within
aztec-nargo
we want to perform postprocessing.Implementation Steps
Tasks
The text was updated successfully, but these errors were encountered: