-
Notifications
You must be signed in to change notification settings - Fork 111
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
ConstantUsageCheck error message is misleading #260
Comments
I'll ask someone to take care of this task soon |
@carlosmiranda thanks for reporting! I topped your account for 15 mins, transaction 40144614 |
@krzyk the issue is yours, please help |
@carlosmiranda Fix has been merged, please close this issue. |
@krzyk Looks good, thanks! |
@davvd ping |
@krzyk thanks, I just added 15 mins to your account, payment |
these 2 puzzles were created in this ticket: |
@carlosmiranda the puzzle #1124 is still not solved. |
ConstantUsageCheck
has the following message if it detects a violation:It's misleading. ConstantUsageCheck actually enforces that a private field be used at least twice, so it'll also be triggered for unused constants. Let's re-word it to reflect this behavior or otherwise show an alternative message for unused constants.
The text was updated successfully, but these errors were encountered: