We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
In the following example, both contracts have the same outcome, but slither detects an initialized variable in Reference:
Reference
contract Reference{ mapping (uint128 => mapping (uint256 => uint256)) map; function init() external{ mapping(uint256 => uint256) tmp = map[0]; tmp[0] = 0; } } contract Direct{ mapping (uint128 => mapping (uint256 => uint256)) map; function init() external{ map[0][0] = 0; } }
The issue is that slither does not track the storage reference created through mapping(uint256 => uint256) tmp = map[0];, while it should.
mapping(uint256 => uint256) tmp = map[0];
It is close to the issue #70
The text was updated successfully, but these errors were encountered:
The alias analysis is merged in master, this FP is not anymore reported
Sorry, something went wrong.
No branches or pull requests
In the following example, both contracts have the same outcome, but slither detects an initialized variable in
Reference
:The issue is that slither does not track the storage reference created through
mapping(uint256 => uint256) tmp = map[0];
, while it should.It is close to the issue #70
The text was updated successfully, but these errors were encountered: