Impl.TypMappings from OCaml types to R1CS variables and constraints.
type ('var, 'value, 'aux) typ' = ( 'var, 'value, 'aux ) Internal_Basic.Typ.typ' =
{var_to_fields : 'var -> Internal_Basic.field_var array * 'aux; |
var_of_fields : (Internal_Basic.field_var array * 'aux) -> 'var; |
value_to_fields : 'value -> Internal_Basic.field array * 'aux; |
value_of_fields : (Internal_Basic.field array * 'aux) -> 'value; |
size_in_field_elements : int; |
constraint_system_auxiliary : unit -> 'aux; |
check : 'var -> unit Internal_Basic.Checked.t; |
}type ('var, 'value) typ = ( 'var, 'value ) Internal_Basic.Typ.typ = | Typ : ( 'var, 'value, 'aux ) typ' -> ( 'var, 'value ) typ |
module Data_spec : sig ... endtype ('var, 'value) t = ( 'var, 'value ) typThe type ('var, 'value) t describes a mapping from the OCaml type 'value to a type representing the value using R1CS variables ('var). This description includes
Store.t for storing 'values as 'varsAlloc.t for creating a 'var when we don't know what values it should contain yetRead.t for reading the contents of the 'var back out as a 'value in As_prover blocksChecked.t for asserting constraints on the 'var -- for example, that a Boolean.t is either a Field.zero or a Field.one.Basic instances:
val unit : ( unit, unit ) tval field : ( Internal_Basic.field_var, Internal_Basic.field ) tCommon constructors:
synonym for tuple2
list ~length typ describes how to convert between a 'value list and a 'var list, given a description of how to convert between a 'value and a 'var.
length must be the length of the lists that are converted. This value must be constant for every use; otherwise the constraint system may use a different number of variables depending on the data given.
Passing a list of the wrong length throws an error.
array ~length typ describes how to convert between a 'value array and a 'var array, given a description of how to convert between a 'value and a 'var.
length must be the length of the arrays that are converted. This value must be constant for every use; otherwise the constraint system may use a different number of variables depending on the data given.
Passing an array of the wrong length throws an error.
val hlist :
( unit, unit, 'k_var, 'k_value ) Data_spec.t ->
( ( unit, 'k_var ) H_list.t, ( unit, 'k_value ) H_list.t ) tUnpack a Data_spec.t list to a t. The return value relates a polymorphic list of OCaml types to a polymorphic list of R1CS types.
Convert relationships over isomorphic types:
val of_hlistable :
( unit, unit, 'k_var, 'k_value ) Data_spec.t ->
var_to_hlist:( 'var -> ( unit, 'k_var ) H_list.t ) ->
var_of_hlist:( ( unit, 'k_var ) H_list.t -> 'var ) ->
value_to_hlist:( 'value -> ( unit, 'k_value ) H_list.t ) ->
value_of_hlist:( ( unit, 'k_value ) H_list.t -> 'value ) ->
( 'var, 'value ) tA specialised version of transport/transport_var that describes the relationship between 'var and 'value in terms of a Data_spec.t.
type 'a prover_value = 'a Internal_Basic.Typ.prover_valueval prover_value : unit -> ( 'a prover_value, 'a ) tA Typ.t for marshalling OCaml values generated in As_prover blocks, while keeping them opaque to the Checked world.
This is the dual of snarkless, which allows OCaml values from the Checked world to pass through As_prover blocks.