-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
#663: Fixed bitcount operations #699
#663: Fixed bitcount operations #699
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, it's more cleaner than prior implementation.
@JyotinderSingh shall we merge this?
@VedWhat on other note what are your thoughts on using go inbuilt function i.e. OnesCount8 rather than the popcount
implementation?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. Few minor comments.
257ba8b
to
9415d55
Compare
Nice, makes sense to use a lookup instead of any operations. Made the change! |
thanks, could you take a look at the linter issues too? |
right, was pushing with a no-verify due to an issue. already pushed the change. |
This PR attempts to close #663 however I realised rewrite would be a better option. This passes all tests under tcl (only for bitcount) and all integration tests. While this also fixes other issues, I don't want to overstep.
I've added comments wherever necessary but can elaborate wherever necessary
What has changed?
@lucifercr07 as mentioned, this does fix the other bitcount issues, lmk what you think. I believe this is a better way to fix the errors (fixing a single test would've made it messier if you get what I mean)
Happy to change the approach just to fix the single test.