fix: remove dup arg in template builder for SetDelete (#430)
* fix: remove dup arg in template builder for SetDelete * fix typo * remove dbg
This commit is contained in:
parent
352b1fdac1
commit
ffed5b4fbd
3 changed files with 5 additions and 10 deletions
|
|
@ -148,7 +148,6 @@ impl MockMainPod {
|
||||||
|
|
||||||
pub fn new(params: &Params, inputs: MainPodInputs) -> Result<Self> {
|
pub fn new(params: &Params, inputs: MainPodInputs) -> Result<Self> {
|
||||||
let (statements, public_statements) = layout_statements(params, true, &inputs)?;
|
let (statements, public_statements) = layout_statements(params, true, &inputs)?;
|
||||||
dbg!(public_statements.len());
|
|
||||||
let mut aux_list = vec![OperationAux::None; params.max_priv_statements()];
|
let mut aux_list = vec![OperationAux::None; params.max_priv_statements()];
|
||||||
// Extract Merkle proofs and pad.
|
// Extract Merkle proofs and pad.
|
||||||
let merkle_proofs =
|
let merkle_proofs =
|
||||||
|
|
|
||||||
|
|
@ -119,14 +119,10 @@ impl StatementTmplBuilder {
|
||||||
predicate: Predicate::Native(NativePredicate::ContainerDelete),
|
predicate: Predicate::Native(NativePredicate::ContainerDelete),
|
||||||
args: self.args,
|
args: self.args,
|
||||||
},
|
},
|
||||||
Predicate::Native(NativePredicate::SetDelete) => {
|
Predicate::Native(NativePredicate::SetDelete) => StatementTmplBuilder {
|
||||||
let mut new_args = self.args.clone();
|
predicate: Predicate::Native(NativePredicate::ContainerDelete),
|
||||||
new_args.push(self.args[2].clone());
|
args: self.args,
|
||||||
StatementTmplBuilder {
|
},
|
||||||
predicate: Predicate::Native(NativePredicate::ContainerDelete),
|
|
||||||
args: new_args,
|
|
||||||
}
|
|
||||||
}
|
|
||||||
_ => self,
|
_ => self,
|
||||||
}
|
}
|
||||||
}
|
}
|
||||||
|
|
|
||||||
|
|
@ -2,7 +2,7 @@
|
||||||
//! from the feature-enabled backend.
|
//! from the feature-enabled backend.
|
||||||
//!
|
//!
|
||||||
//! This is done in order to avoid inconsistencies where a type or parameter is defined in the
|
//! This is done in order to avoid inconsistencies where a type or parameter is defined in the
|
||||||
//! middleware to have certain carachteristic and later in the backend it gets used differently.
|
//! middleware to have certain characteristic and later in the backend it gets used differently.
|
||||||
//! The idea is that those types and parameters (eg. lengths) have a single source of truth in the
|
//! The idea is that those types and parameters (eg. lengths) have a single source of truth in the
|
||||||
//! code; and in the case of the "base types" this is determined by the backend being used under
|
//! code; and in the case of the "base types" this is determined by the backend being used under
|
||||||
//! the hood, not by a choice of the middleware parameters.
|
//! the hood, not by a choice of the middleware parameters.
|
||||||
|
|
|
||||||
Loading…
Add table
Add a link
Reference in a new issue