Zokyo Gas Savings
  • โ›ฝZokyo Gas Savings
  • ๐Ÿ“šTutorials
    • โœ”๏ธGas Saving Technique 1: Unchecked Arithmetic
    • โ›“๏ธGas Saving Technique 2: Immutable Variable
    • โœจGas Saving Technique 3: Double star ** inefficiency
    • ๐Ÿ’ฐGas Saving Technique 4: Cache Array Length
    • โฌ…๏ธGas Saving Technique 5: ++i costs less gas compared to i++
    • โš–๏ธGas Saving Technique 6: NOT operator ! cheaper than boolean FALSE
    • ๐ŸชกGas Saving Technique 7: Using Short Reason Strings
    • ๐ŸชตGas Saving Technique 8: Use Custom Errors instead of Revert Strings to save Gas
    • โœ’๏ธGas Saving Technique 9: Use Custom Errors instead of Revert Strings to save Gas
    • ๐Ÿ‘พGas Saving Technique 10: Calldata cheaper than memory
    • โ›”Gas Saving Technique 11: > 0 is less efficient than != 0 for unsigned integers
    • โž—Gas Saving Technique 12: SafeMath no longer needed
    • ๐Ÿ˜ฎGas Saving Technique 13: variables default to 0
    • ๐ŸงฑGas Saving Technique 14: struct layout/ variable packing
    • ๐Ÿ“žGas Saving Technique 15: Cache External Call
    • โœ๏ธGas Saving Technique 16: Early Validation before external call
    • ๐Ÿ˜ŽGas Saving Technique 17: Donโ€™t cache value that is used once
    • ๐Ÿ˜งGas Saving Technique 18: Redundant code
    • โœ…Gas Saving Technique 19: Early Validation before external call
    • โ›๏ธGas Saving Technique 20: Storage vs Memory read optimizations
    • โœ’๏ธGas Saving Technique 21: Unneeded If statements
    • ๐ŸŒ—Gas Saving Technique 22: >= is cheaper than >
    • ๐ŸŽ’Gas Saving Technique 23: Public to private constants
    • โน๏ธGas Saving Technique 24: Make unchanged variables constant/immutable
    • โฑ๏ธGas Saving Techniques 25: Redundant Access Control Checks
    • โžก๏ธGas Saving Technique 26: Shift Right instead of Dividing by 2
    • ๐ŸชƒGas Saving Tutorial 27: Efficient Boolean Comparison
    • ๐ŸคGas Saving Technique 28: && operator uses more gas
    • ๐Ÿ‘“Gas Saving Technique 29: x = x + y is cheaper than x += y
    • ๐Ÿ‘‚Gas Saving Technique 30: Using 1 and 2 rather than 0 and 1 saves gas
    • โšฝGas Saving Technique 31: Optimize Storage by Avoiding Booleans
    • ๐Ÿ”™Gas Saving Technique 32: Optimal Use of Named Return Variables in Solidity
    • ๐Ÿ›ข๏ธGas Saving Technique 33: Making Functions Payable for Optimized Gas Costs
    • โœ๏ธGas Saving Technique 34: Optimizing Storage References in Smart Contracts
    • โ›ฐ๏ธGas Saving Technique 35: Usage of uints/ints smaller than 32 bytes (256 bits) incurs overhead
    • ๐ŸŒช๏ธGas Saving Technique 36: Inlining Single Use Internal Functions for Savings
    • โ˜„๏ธGas Saving Technique 37: Switching from Public to External Functions for Savings
    • ๐ŸŽ†Gas Saving Technique 38: Upgrading Solidity Compiler to Improve Gas Efficiency and Security
    • ๐Ÿ•ถ๏ธGas Saving Technique 39: Avoiding Duplicated Code for Gas Savings
    • ๐Ÿ˜„Gas Saving Technique 40: Removal of Unused Internal Functions for Gas Savings
    • ๐Ÿ–‹๏ธGas Saving Tutorial 41: In-lining Single Use Modifiers For Gas Saving
    • โ›๏ธGas Saving Technique 42: `require` vs`assert`
Powered by GitBook
On this page
  1. Tutorials

Gas Saving Technique 32: Optimal Use of Named Return Variables in Solidity

PreviousGas Saving Technique 31: Optimize Storage by Avoiding BooleansNextGas Saving Technique 33: Making Functions Payable for Optimized Gas Costs

Last updated 1 year ago

Introduction: In Solidity, function return values can be explicitly named, creating named return variables. While they provide clarity, misuse can lead to redundant operations and increased gas costs. This tutorial will dive into the efficient use of named return variables for both code readability and gas optimization.


Concept:

  1. Named Return Variables: When defining functions in Solidity, it's possible to give names to return variables. This can enhance readability and reduce code redundancy.

  2. Redundant Return Statements: If a function has named return variables and also includes an explicit return statement, it can result in both redundancy and extra gas costs.


Examples & Recommendations:

Consider the code snippets from StakedCitadelLocker.sol:

  1. Before Optimization:

    solidityCopy codefunction getRewards() external returns (uint256 userRewards) {
        // ... some logic that sets userRewards ...
        return userRewards;
    }
  2. After Optimization:

    solidityCopy codefunction getRewards() external returns (uint256 userRewards) {
        // ... some logic that sets userRewards ...
    }

Note: When using named return variables, the value assigned to them gets automatically returned at the end of the function. Explicitly returning them is redundant.


Step-by-Step Guide for Implementing the Named Return Variable Optimization:

  1. Identification: Scan your contract for functions that define named return variables and also use an explicit return statement.

  2. Removal: For each identified function, remove the explicit return statement. Ensure the logic correctly assigns the value to the named return variable, as it will be automatically returned.

  3. Verification: Review each optimized function to confirm that the logic remains intact.

  4. Testing: Thoroughly test the contract to ensure that functions still behave as expected and return the correct values.


Benefits:

  1. Gas Savings: Removing unnecessary return statements can save gas during contract deployment and execution.

  2. Code Readability: By avoiding redundancy and utilizing named return variables, the code remains clean and intent-driven.


Conclusion: The use of named return variables in Solidity can provide clarity and improved readability. However, care must be taken to avoid redundancies like unnecessary return statements, which can lead to gas inefficiencies. By efficiently using named return variables, developers can maintain clean code while also optimizing for gas savings.

๐Ÿ“š
๐Ÿ”™
Book an audit with Zokyo