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
Describe the false alarm that Slither raise and how you know it's inaccurate:
When using the variable for slicing bytes calldata slither can't recognise my constants are being used. The minimal reproducible code below triggers unused-state-variables for every constant except for _OPERATION_CODE_END that is used in the if statement. This does not seem to be related with #112.
INFO:Detectors:
SlitherFails._OPERATION_CODE_START (src/slither.sol#7) is never used in SlitherFails (src/slither.sol#6-23)
SlitherFails._OFFSET_NUM1 (src/slither.sol#10) is never used in SlitherFails (src/slither.sol#6-23)
SlitherFails._OFFSET_NUM2 (src/slither.sol#11) is never used in SlitherFails (src/slither.sol#6-23)
Reference: https://github.com/crytic/slither/wiki/Detector-Documentation#unused-state-variable
The text was updated successfully, but these errors were encountered:
This is caused by our oversimplification of array slices that does not keep track off the start/stop and consider it as read.
We will need to probably represent IndexRangeAccess in slithIR to fix
ref #1096
Describe the false alarm that Slither raise and how you know it's inaccurate:
When using the variable for slicing bytes calldata slither can't recognise my constants are being used. The minimal reproducible code below triggers
unused-state-variables
for every constant except for_OPERATION_CODE_END
that is used in the if statement. This does not seem to be related with #112.Frequency
Occasionally
Code example to reproduce the issue:
Version:
0.10.0
Relevant log output:
The text was updated successfully, but these errors were encountered: