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.

Sign up for GitHub

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

Jump to bottom

Have our own Field trait? #221

Open
mimoo opened this issue Nov 6, 2024 · 1 comment
Open

Have our own Field trait? #221

mimoo opened this issue Nov 6, 2024 · 1 comment
Labels
discussion

Comments

@mimoo
Copy link
Contributor

mimoo commented Nov 6, 2024

I'm not sure anymore why we rely on arkworks here. Arkworks comes with a complicated number of traits and a lack of support for serde. In addition different backends might use different versions of arkworks (we've had that problem).

IMO we should have our own Field trait that has a minimal definition, and then we can convert to whatever a backend uses at the right time in the compilation process.
@katat
Copy link
Collaborator

katat commented Nov 8, 2024

Agreed, we could just add a number of interfaces to the existing BackendField trait.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
discussion
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@mimoo @katat