Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: reorganize cli params #432

Merged

Conversation

atanmarko
Copy link
Member

@atanmarko atanmarko commented Jul 23, 2024

Resolves #426

@atanmarko atanmarko self-assigned this Jul 23, 2024
@github-actions github-actions bot added the crate: zero_bin Anything related to the zero-bin subcrates. label Jul 23, 2024
@atanmarko atanmarko added this to the Misc. milestone Jul 23, 2024
@atanmarko atanmarko marked this pull request as ready for review July 23, 2024 15:10
Copy link
Collaborator

@Nashtare Nashtare left a comment

Choose a reason for hiding this comment

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

Thanks Marko, much cleaner! I just have some comments (non-blocking) open to discussion, other LGTM.

zero_bin/prover/src/cli.rs Outdated Show resolved Hide resolved
zero_bin/prover/src/cli.rs Outdated Show resolved Hide resolved
zero_bin/prover/src/lib.rs Outdated Show resolved Hide resolved
@@ -20,9 +22,11 @@ use tracing::info;
use zero_bin_common::fs::generate_block_proof_file_name;

#[derive(Debug, Clone, Copy)]
pub struct ProverParams {
pub struct ProverConfig {
Copy link
Collaborator

Choose a reason for hiding this comment

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

Do we actually need to have a ProverConfig anymore, given that it is semantically identical to CliProverConfig, and that all fields are guaranteed to be initialized?

Copy link
Member Author

Choose a reason for hiding this comment

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

@Nashtare I don't much like the idea of clap structure (CliProverConfig) being passed as an argument deep in the stack, but yeah, we can remove ProverConfig.

Copy link
Collaborator

Choose a reason for hiding this comment

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

Yeah I guessed you'd answer something along these lines 🙃
I'm not strongly opinionated, we can keep the distinction.

@atanmarko atanmarko merged commit e09916f into feat/optimize-segment-proof-aggregation Jul 23, 2024
11 of 14 checks passed
@atanmarko atanmarko deleted the feat/reortanize-cli-params branch July 23, 2024 15:53
@Nashtare Nashtare restored the feat/reortanize-cli-params branch August 1, 2024 15:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
crate: zero_bin Anything related to the zero-bin subcrates.
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

2 participants