pub struct Command<'a> {
pub _tab: Table<'a>,
}Expand description
Optional: Command messages can be used to request actions from the receiver. This makes it possible to write code that works in different environments. Commands and parameters can be passed over the same byte stream as other messages; if so Command must be the first message. This reduces the need for environment-specific methods (it can replace CLI –flags, etc).
Fields§
§_tab: Table<'a>Implementations§
Source§impl<'a> Command<'a>
impl<'a> Command<'a>
pub const VT_CONSTRAINTS_GENERATION: VOffsetT = 4i16
pub const VT_WITNESS_GENERATION: VOffsetT = 6i16
pub const VT_PARAMETERS: VOffsetT = 8i16
pub fn init_from_table(table: Table<'a>) -> Self
pub fn create<'bldr: 'args, 'args: 'mut_bldr, 'mut_bldr>( _fbb: &'mut_bldr mut FlatBufferBuilder<'bldr>, args: &'args CommandArgs<'args>, ) -> WIPOffset<Command<'bldr>>
Sourcepub fn constraints_generation(&self) -> bool
pub fn constraints_generation(&self) -> bool
For gadget flows.
Request the generation of a constraint system (or part thereof).
If true, this must be followed by a CircuitHeader.
The response must be another CircuitHeader message with a greater free_variable_id
followed by one or more ConstraintSystem messages.
Sourcepub fn witness_generation(&self) -> bool
pub fn witness_generation(&self) -> bool
For gadget flows.
Request the generation of a witness (or part thereof).
If true, this must be followed by a CircuitHeader, and the instance_variables
variables must contain input values.
The response must be another CircuitHeader message, with a greater free_variable_id,
with output values in instance_variables, followed by one or more Witness messages.
Sourcepub fn parameters(&self) -> Option<Vector<'a, ForwardsUOffset<KeyValue<'a>>>>
pub fn parameters(&self) -> Option<Vector<'a, ForwardsUOffset<KeyValue<'a>>>>
Optional: Any complementary parameter that may be useful.