Hygiene: Add MESSAGE_STORAGE. No leak Uint32/64 #91
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
PENDING: I'm still editing this PR. I will remove this once done.
Three hygiene changes:
MESSAGE_STORAGE
which was used as aCapnp.Message.Make
functor parameter but was previously hidden in
Capnp__MessageStorage.S
. (I say "hidden" becauseMessageStorage
is not being exported by thecapnp.ml
wrapper, so a user has to hack into Dune internals to get access to theS
module type.)Uint32
andUint64
in module types.ListStorageType
. TheCapnp.MessageSig.S
is public (aka. part of wrapped capnp.ml) and has a ListStorage module. But ListStorage.t has a storage_type field of typeCapnp.MessageSig.ListStorageType.t
that was not public.The first one is important since my MlFront analysis tool has a security posture that does not allow external access to double underscore (private) modules.
The second one is part of a broader issue that there are few
.mli
files incapnp-ocaml
. That means unnecessary modules, types and values leak. This PR only addresses the one leak that is very visible to me.The third one is similar to the first one.