Skip to content

fix: range checker should handle edge cases separately #911

Open
@ivokub

Description

@ivokub

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)

Metadata

Metadata

Assignees

Labels

bugSomething isn't working

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions