detector for storage optimizations by reordering struct variables#1346
detector for storage optimizations by reordering struct variables#1346mavlevin wants to merge 27 commits into
Conversation
|
|
|
This pull request introduces 1 alert when merging a340075 into a277925 - view on LGTM.com new alerts:
|
|
This pull request introduces 2 alerts when merging 94d5f8a into 243c6da - view on LGTM.com new alerts:
|
|
This pull request introduces 2 alerts when merging e5d172d into 243c6da - view on LGTM.com new alerts:
|
|
This pull request introduces 2 alerts when merging ce03221 into 78397b9 - view on LGTM.com new alerts:
|
|
This pull request introduces 2 alerts when merging 703b023 into 78397b9 - view on LGTM.com new alerts:
|
|
This pull request introduces 2 alerts when merging 94f10f5 into 78397b9 - view on LGTM.com new alerts:
|
|
This pull request introduces 2 alerts when merging 43c44c8 into 78397b9 - view on LGTM.com new alerts:
|
|
This pull request introduces 2 alerts when merging 2b987a2 into 719e4e9 - view on LGTM.com new alerts:
|
|
This pull request introduces 2 alerts when merging 8adeb8d into 719e4e9 - view on LGTM.com new alerts:
|
|
This pull request introduces 2 alerts when merging 2d7099d into 440ac4b - view on LGTM.com new alerts:
|
|
|
||
| WIKI = "https://github.com/trailofbits/slither/wiki/optimal-variable-order" | ||
| WIKI_TITLE = "Optimal Variable Order" | ||
| WIKI_DESCRIPTION = "Detect optimal variable order in contract storage layouts and struct definitions to decrease the number of slots used." |
There was a problem hiding this comment.
This description seems to indicate that the script will actually find an optimal ordering, but it's not guaranteed. The algorithm is only heuristic, so there may be tighter packings.
4 participants
No description provided.