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

ZeroState vs Allocate #513

Open
mpharrigan opened this issue Nov 13, 2023 · 1 comment · Fixed by #619
Open

ZeroState vs Allocate #513

mpharrigan opened this issue Nov 13, 2023 · 1 comment · Fixed by #619

Comments

@mpharrigan
Copy link
Collaborator

These two things result in confusion. Especially since there's an unused/unsupported n attribute in ZeroState. I suggest removing this and making ZeroState always a one-bit thing for use in smaller circuits and bit twiddling. Maybe rename to ZeroBitState? That's pretty long though. If you just need a bunch of workspace use Allocate or its convenience method bb.alloc(). If you need a particular integer there's IntState.

@mpharrigan
Copy link
Collaborator Author

Un-closing. We should remove n from ZeroState.

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