pbennett
commented
2 years ago This would be VERY valuable actually. I'd like to see compilation as you mentioned produce the named TMPL_XX byte offsets as a json array in a json object return for eg. Would this be kind of a partial compilation? I'd want to be able to pass teal as-is w/ TMPL_XX placeholders and get the real bytecode back but w/ insertion offsets (which I could adjust for as I inserted) for each of the parameters. This way I could compile the TEAL once and cache it, then replace the parameters efficiently without having to recompile.
barnjamin
There are 2 valuable bits of information the are available during contract assembly.
1) Program Counter (pc), the index in the bytecode of a given instruction 2) Template Variable Locations, the index in the bytecode of a given template variable and its type
Producing an output file with the above would help with debugging and with variable insertion.
More tooling for encoding and inserting template variables would be needed as well.