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

[post frontend-backend split] Move types/functions from common to frontend/backend #266

Closed
ed255 opened this issue Feb 2, 2024 · 6 comments
Assignees

Comments

@ed255
Copy link
Member

ed255 commented Feb 2, 2024

After the frontend-backend split a new package halo2_common was added that contains functions and types used by both frontend and backend. These functions/types are now pub but are meant for internal usage only of the halo2 repository.

As future work we should try to move more stuff to either frontend/backend, creating mirror lightweight types as necessary; or splitting functionality between frontend and backend. After types/functions are moved to frontend/backend, they should recover the pub(crate) status.

Here's a non-exhaustive list of affected types:

Blocked by #254

@ed255
Copy link
Member Author

ed255 commented Feb 20, 2024

I'm currently working on halo2_common::plonk::circuit::Expression (and will also probably work on the halo2_common::plonk::circuit::ConstraintSystem.
My current approach is to define a single Expression type that can be generic and instantiated into 2 cases: one for the frontend, and one for the backend.

@duguorong009
Copy link

duguorong009 commented Feb 21, 2024

I work on task - move halo2_common::arithmetic to halo2_backend. #281

@duguorong009
Copy link

I work on task - move plonk::Challenge* & plonk::transcript from common to backend. #287

@ed255
Copy link
Member Author

ed255 commented Mar 18, 2024

@duguorong009 will work on the remaining points of this issue.

@duguorong009
Copy link

@ed255
I've just merged the #298 .
After this, there is no halo2_common crate(the post-split tech debt) in the repo.
Hence, I think we can close this issue as completed.

What do you think?

@ed255
Copy link
Member Author

ed255 commented Mar 22, 2024

@ed255 I've just merged the #298 . After this, there is no halo2_common crate(the post-split tech debt) in the repo. Hence, I think we can close this issue as completed.

What do you think?

I agree! This issue has now been completed, I'll just close it; thanks for the reminder!

@ed255 ed255 closed this as completed Mar 22, 2024
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

No branches or pull requests

2 participants