feat!: Internal as a macro - #4898
Conversation
Benchmark resultsMetrics with a significant change:
Detailed resultsAll benchmarks are run on txs on the This benchmark source data is available in JSON format on S3 here. Values are compared against data from master at commit L2 block published to L1Each column represents the number of txs on an L2 block published to L1.
L2 chain processingEach column represents the number of blocks on the L2 chain where each block has 16 txs.
Circuits statsStats on running time and I/O sizes collected for every circuit run across all benchmarks.
Tree insertion statsThe duration to insert a fixed batch of leaves into each tree type.
MiscellaneousTransaction sizes based on how many contracts are deployed in the tx.
Transaction processing duration by data writes.
|
1435d81 to
e3130fd
Compare
Docs PreviewHey there! 👋 You can check your preview at https://65e72a6c18b65a236589e8d9--aztec-docs-dev.netlify.app |
left a comment
There was a problem hiding this comment.
lgtm, cc @TomAFrench on the frontend changes
|
I'm fine with this. We'll probably remove the concept of a function being internal in future and just attach the function's custom attributes into the build artifact, so we don't need to thread knowledge of an aztec concept through the compiler. Could we follow this up with another PR which makes the same change for the |
it should be quick to remove, the #[aztec(public)] already adds |
Implement internal functions as a macro. Internal functions are now written with an
aztec(internal)decorator as opposed to theinternalkeyword.