Bytecode size blowup not completely resolved

[benesjan]

A while ago I stumbled upon a bytecode size issues when re-constraining encryption in a token contract. This is the original post on slack:

After re-constraining encryption token contract artifact size blows up from 4.8MB to 125MB. When I look inside the artifact the culprit lies in bytecode and debug_symbols sizes of the changed functions. (e.g. one of those functions is transfer_to_public where bytecode blows up to more than 20 MB and debug_symbols to more than 9 MB).

After rebasing that PR on master there was a significant improvement and the bytecode size dropped to 50MB (noir-projects/noir-contracts/target/token_contract-Token.json file).

This however still causes some of the tests to fail (when fetching the bytecode from aztec node).

it seems to me that the bytecode is still too big and the bytecode size blowup issue have not been completely resolved.

Nargo Version

nargo version = 1.0.0-beta.0 noirc version = 1.0.0-beta.0+644ac8064bf63de3 (git version hash: 644ac8064bf63de3, is dirty: false)

[aakoshh]

For reference this method was also the one responsible for the increase investigated in #6786