-
Notifications
You must be signed in to change notification settings - Fork 170
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
reason-string
rule incorrectly handles revert
#157
Comments
PR here: #158 |
Closed by #158. |
boolafish
added a commit
to omgnetwork/plasma-contracts
that referenced
this issue
Oct 2, 2019
Remove this comment: "// solhint-disable-next-line reason-string" as the issue is solved. solhint bug: protofire/solhint#157
boolafish
added a commit
to omgnetwork/plasma-contracts
that referenced
this issue
Oct 2, 2019
Remove this comment: "// solhint-disable-next-line reason-string" as the issue is solved. solhint bug: protofire/solhint#157
boolafish
added a commit
to omgnetwork/plasma-contracts
that referenced
this issue
Oct 4, 2019
Remove this comment: "// solhint-disable-next-line reason-string" as the issue is solved. solhint bug: protofire/solhint#157
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The
reason-string
rule checks that calls torequire
andrevert
include an optional message string. It works fine forrequire
calls, but not forrevert
.The issue is that the rule incorrectly treats both calls as if they took 2 arguments, whereas
revert
only takes one (the reason string). Solidity docsSo this works as expected:
but this causes a warning when it shouldn't:
and this passes solhint, but is actually a compile error:
The text was updated successfully, but these errors were encountered: