package tezos-protocol-environment

  1. Overview
  2. Docs
Interface layer between the protocols and the shell

Install

Dune Dependency

Authors

Maintainers

Sources

tezos-16.1.tar.gz
sha256=43723d096307603703a1a89ed1b2eb202b365f5e7824b96b0cbf813b343a6cf7
sha512=b2a637f2e965000d3d49ad85277ca24d6cb07a1a7cf2bc69d296d8b03ad78c3eaa8e21e94b9162e62c2e11649cd03bc845b2a3dafe623b91065df69d47dc8e4f

doc/tezos-protocol-environment.structs/Tezos_protocol_environment_structs/V4/Replicated_signatures/index.html

Module V4.Replicated_signaturesSource

We have to duplicate the content of src/lib_protocol_environment/sigs/v3/set.mli (and a few other signatures from the same directory) so we can refer to them in src/lib_protocol_environment/environment_V3.ml. Indeed, it is impossible to refer to components of Tezos_protocol_environment_sigs.V3.T (such as the Set component) because T is a module type (not a module).

It might be possible to change the way that the signatures are exported and thus allow access to some of the sub-components, at which point this whole file can be removed. Note, however, that some components make reference to others (e.g., here we need to introduce the type error_monad_trace which we then substitute for Error_monad.trace) so simply exporting the components will not suffice because there will be unbound types.

Ultimately, it might be easier to provide each struct as a partial or full set of legacy libraries which used to be present at the time the environment was made. For the signatures below, we would include a full implementation of Lwtreslib as it appeared when the environment v3 was cut.

Sourcemodule Compare : sig ... end
Sourcemodule Set : sig ... end
Sourcemodule Map : sig ... end
OCaml

Innovation. Community. Security.