package tezos-protocol-environment
Install
Dune Dependency
Authors
Maintainers
Sources
sha256=ad9e08819871c75ba6f4530b125f7d157799398e4d77a1e6bfea9d91ff37ff55
sha512=c5dc4d40cc09bc6980fbbdb5c2e105bf4252cf9cfcb2b49660b0ebe4dc789f6709ec3b3bf2f87d81580d3eed9521eeb1c960f24d9b14eb0285aaba1f84d10a9b
doc/tezos-protocol-environment.structs/Tezos_protocol_environment_structs/V4/Replicated_signatures/index.html
Module V4.Replicated_signatures
Source
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.