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
octalLiteral warns when binary literal is used #1149
Comments
Thanks for reporting, will try to fix today 😉 |
Have tried in the latest go-critic and do not see a problem, can you share what version do you use? how does the error looks like? thanks. |
We need to add some base-2 literals to our negative tests suite for octalLiteral anyway. |
I am using mirror/cron.go:18:11: octalLiteral: suspicious octal args in `uint8(0b_00000001)` (gocritic)
bit1 = uint8(0b_00000001) |
It looks like it's a warning from the old go-critic version. |
Cover binary literals. Also updated a version of golang tools to avoid issues with newer Go versions. Fixes #1149
Cover binary literals. Also updated a version of golang tools to avoid issues with newer Go versions. Fixes #1149
This binary literal looks clear enough to distinguish from normal digits, but we got "octalLiteral" warning. go-critic should fix this warning for binary literals.
The text was updated successfully, but these errors were encountered: