Skip to content
Draft
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -28,12 +28,16 @@ where
ECCConfig: Config,
ECCConfig::FieldConfig: FieldEngine<CircuitField = F::CircuitField>,
{
eprintln!("Exporting to expander circuit...");
let mut expander_circuit = kernel.layered_circuit().export_to_expander().flatten();
expander_circuit.pre_process_gkr();
eprintln!("Expander circuit exported, n_layers = {}", expander_circuit.layers.len());

eprintln!("Preparing prover scratch pad...");
let (max_num_input_var, max_num_output_var) = super::utils::max_n_vars(&expander_circuit);
let prover_scratch =
ProverScratchPad::<F>::new(max_num_input_var, max_num_output_var, mpi_world_size);
eprintln!("Prover scratch pad prepared");
Comment on lines +31 to +40
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

This PR adds many eprintln! calls for logging and debugging. While useful during development, they will print to stderr in all builds, which can be noisy and may have a performance impact. It would be better to use a dedicated logging framework like tracing or log. This allows controlling log output via levels (e.g., trace, debug, info) and enabling/disabling it easily for different build configurations (e.g., release vs. debug).


(expander_circuit, prover_scratch)
}
Expand Down
Original file line number Diff line number Diff line change
@@ -1,4 +1,3 @@
pub mod api_no_oversubscribe;
pub mod profiler;
pub mod prove_impl;
pub mod server_fn;

This file was deleted.

Loading
Loading