chore: fix some circular imports - #4445
Conversation
260567a to
6beede8
Compare
Benchmark resultsNo metrics with a significant change found. 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.
|
This PR fixes the circular imports in circuits.js, circuit-types,
archiver and also rewrites imports in foundation to be consistent (there
were a couple of instances of files in foundation that did `import { x }
from '@aztec/foundation'`).
This PR fixes the circular imports in circuits.js, circuit-types,
archiver and also rewrites imports in foundation to be consistent (there
were a couple of instances of files in foundation that did `import { x }
from '@aztec/foundation'`).
This PR fixes the circular imports in circuits.js, circuit-types, archiver and also rewrites imports in foundation to be consistent (there were a couple of instances of files in foundation that did
import { x } from '@aztec/foundation').