You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: slither/detectors/attributes/const_functions_asm.py
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -25,7 +25,7 @@ class ConstantFunctionsAsm(AbstractDetector):
25
25
Functions declared as `constant`/`pure`/`view` using assembly code.
26
26
27
27
`constant`/`pure`/`view` was not enforced prior to Solidity 0.5.
28
-
Starting from Solidity 0.5, a call to a `caonstant`/`pure`/`view` function uses the `STATICCALL` opcode, which reverts in case of state modification.
28
+
Starting from Solidity 0.5, a call to a `constant`/`pure`/`view` function uses the `STATICCALL` opcode, which reverts in case of state modification.
29
29
30
30
As a result, a call to an [incorrectly labeled function may trap a contract compiled with Solidity 0.5](https://solidity.readthedocs.io/en/develop/050-breaking-changes.html#interoperability-with-older-contracts)."""
0 commit comments