cleanup

Author: vezenovm

noir-projects/noir-contracts/contracts/test/public_fns_with_emit_repro_contract/src/main.nr

@@ -5,8 +5,7 @@ use aztec::macros::aztec;
 /// 15 `#[external("public")]` functions, each doing one storage read, one storage write,
 /// and one `self.emit(Updated { .. })`. Pinned here so that:
 ///   - `nargo expand` is snapshotted in `noir-projects/contract-snapshots`, making any
-///     change to the `self.emit(event)` -> `emit_event_in_public(...)` macro rewrite
-///     visible across all 15 call sites in a single review.
+///     change to the macro boilerplate visible across all 15 call sites in a single review.
 ///   - `bytecodeSizeBytes/PublicFnsWithEmitRepro` lands on the bench dashboard, so any
 ///     improvement (or regression) in the per-public-fn emit shape is tracked over time.
 #[aztec]

yarn-project/simulator/src/public/public_tx_simulator/apps_tests/bench.test.ts

@@ -138,11 +138,7 @@ describe('Public TX simulator apps tests: benchmarks', () => {
       });
 
       it('PublicFnsWithEmitRepro contract test', async () => {
-        // Tracks bytecode size of a contract shaped like the public-dispatch repro from
-        // https://github.com/AztecProtocol/aztec-nr/issues/35: 15 public fns, each doing
-        // one storage read, one storage write, and one event emit. None of the other
-        // bench targets exercise this shape, so improvements/regressions in the macro
-        // emit-in-public rewrite would otherwise be invisible on the dashboard.
+        // See comments on the contract source for motivation as to including this contract in our benchmarks.
         tester.setMetricsPrefix(`${metricsPrefixPrefix}PublicFnsWithEmitRepro contract tests`);
         const deployer = AztecAddress.fromNumber(42);