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

fix: range checker should handle edge cases separately #911

Open

ivokub opened this issue Nov 10, 2023 · 0 comments

Assignees

Labels

bug

Collaborator

ivokub commented Nov 10, 2023

Lookup-table based range checker should handle separately cases when requested bits count is 0 or 1:

for 0 bits the input must be 0
for 1 bits the input must be 0 or 1 (perform boolean test)

ivokub added the bug label

ivokub self-assigned this

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment