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
{{ message }}
This repository has been archived by the owner on Mar 7, 2024. It is now read-only.
I have been working on implementing Bulletproofs in Hacspec, but the algorithm is fairly long. I would like to be able to split up a file into smaller bits. Take the following file structure as an example:
I have the three main files as errors.rs, ipp.rs and transcript.rs. Both errors.rs and the transcripts.rs file can easily be reached from the main ipp.rs file using:
mod transcript;use transcript::*;mod errors;use errors::*;
But the transcript.rs file also needs access to the errors.rs file and the above code import would not work. This is also why in the example, there is two errors.rs files, the cursive is a symbolic link to the non-cursive. This does work but it is obviously not ideal.
Googling around how to solve the issue, the following is the accepted way to do it in pure Rust:
usecrate::errors::*;
But this is not allowed in hacspec. Is there another way to do this, and if not, could hacspec support something like what was suggested for pure Rust?
The text was updated successfully, but these errors were encountered:
I have been working on implementing Bulletproofs in Hacspec, but the algorithm is fairly long. I would like to be able to split up a file into smaller bits. Take the following file structure as an example:
I have the three main files as
errors.rs
,ipp.rs
andtranscript.rs
. Botherrors.rs
and thetranscripts.rs
file can easily be reached from the mainipp.rs
file using:But the
transcript.rs
file also needs access to theerrors.rs
file and the above code import would not work. This is also why in the example, there is twoerrors.rs
files, the cursive is a symbolic link to the non-cursive. This does work but it is obviously not ideal.Googling around how to solve the issue, the following is the accepted way to do it in pure Rust:
But this is not allowed in hacspec. Is there another way to do this, and if not, could hacspec support something like what was suggested for pure Rust?
The text was updated successfully, but these errors were encountered: