[Certora Audit] G-04. ExtensibleBase._setSafeMethod(): storage access optimization
#891
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
remedcu
changed the title
ExtensibleBase._setSafeMethod(): storage access optimizationExtensibleBase._setSafeMethod(): storage access optimization
mmv08
approved these changes
Jan 9, 2025
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request includes a refactor to the
_setSafeMethodfunction in theExtensibleBasecontract to improve memory access.The following optimizes the logic and minimizes storage accesses:
contracts/handler/extensible/ExtensibleBase.sol: Modified the_setSafeMethodfunction to use a local variablesafeMethodfor accessing thesafeMethodsmapping, which simplifies and clarifies the code.