Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Seperate our custom implementations from the originally forked #109

Closed
moCello opened this issue May 19, 2023 · 0 comments · Fixed by #113
Closed

Seperate our custom implementations from the originally forked #109

moCello opened this issue May 19, 2023 · 0 comments · Fixed by #113
Assignees

Comments

@moCello
Copy link
Member

moCello commented May 19, 2023

Summary

Currently the original implementation and our additions are intertwined all across the crate. We want to get an overview on the differences (and similarities) between our fork and the original. For this to happen we need a clear separation between the two.

Possible solution design or implementation

Possible add a module in each existing module that extends the original functionalities with our custom ones.

Additional context

Similar efforts are happening on our jubjub implementation, see jubjub issue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant