You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, we expose a way too much things when indeed we should try to expose publicly in the API only the necessary stuff.
We have modules as fft or transcript_protocol which shouldn't be pub.
Also there are quite some structures which are pub but never meant to be used by the lib consumers.
Finally we also have pub fields for structs like Proof when indeed they shouldn't be.
The text was updated successfully, but these errors were encountered:
Currently, we expose a way too much things when indeed we should try
to expose publicly in the API only the necessary stuff.
We have modules as fft or transcript_protocol which shouldn't be pub.
Also there are quite some structures which are pub but never meant to
be used by the lib consumers.
The idea is that with this PR we're able to make more clear which are
the things that the consumer is suposed to call or do.
Closes#438
Currently, we expose a way too much things when indeed we should try
to expose publicly in the API only the necessary stuff.
We have modules as fft or transcript_protocol which shouldn't be pub.
Also there are quite some structures which are pub but never meant to
be used by the lib consumers.
The idea is that with this PR we're able to make more clear which are
the things that the consumer is suposed to call or do.
Closes#438
Currently, we expose a way too much things when indeed we should try to expose publicly in the API only the necessary stuff.
We have modules as
fft
ortranscript_protocol
which shouldn't be pub.Also there are quite some structures which are
pub
but never meant to be used by the lib consumers.Finally we also have
pub
fields for structs likeProof
when indeed they shouldn't be.The text was updated successfully, but these errors were encountered: