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 36: Inlining Single Use Internal Functions for Savings

PreviousGas Saving Technique 35: Usage of uints/ints smaller than 32 bytes (256 bits) incurs overheadNextGas Saving Technique 37: Switching from Public to External Functions for Savings

Last updated 1 year ago

Introduction: Solidity offers both public, private, and internal function visibility. While internal functions offer flexibility in terms of reusability and code organization, if they are only called once, there can be an added overhead. In such cases, inlining these functions can save on the gas cost.


Concept:

  1. Function Calls Overhead: Every function call, even internal ones, comes with a bit of overhead in the EVM.

  2. Inlining: This is a compiler optimization technique where the function's code is expanded in place rather than being called, thereby saving on the overhead associated with the function call.


Examples & Recommendations:

Problem: Having an internal function that's only called once in the contract. Solution: Instead of keeping it as a separate function, its logic can be directly placed (or "inlined") where it's called.

Non-Optimized Approach:

solidityCopy codecontract Example {
    uint256 public value;

    function setValue(uint256 _value) public {
        _internalSet(_value);
    }

    internal function _internalSet(uint256 _newValue) {
        value = _newValue;
    }
}

Optimized (Inlined) Approach:

solidityCopy codecontract Example {
    uint256 public value;

    function setValue(uint256 _value) public {
        value = _value;
    }
}

Step-by-Step Guide for Function Inlining:

  1. Review: Identify internal functions in your contract that are called only once.

  2. Inline the Logic: Replace the single call to the internal function with its logic.

  3. Test: After making the change, ensure that the contract's functionality remains consistent. This is vital, as inlining can sometimes alter behavior if not done carefully.


Benefits:

  1. Gas Efficiency: Eliminate the overhead associated with function calls, resulting in gas savings.

  2. Code Simplicity: Reducing the number of functions can simplify the code, making it easier to read and audit.

  3. Reduced Attack Surface: Fewer functions might lead to a reduced attack surface, as there's less code that can potentially be exploited.


Considerations:

  1. Reusability: If there's a chance the internal function might be used more in future versions or by other contracts inheriting from it, consider keeping it.

  2. Readability: Sometimes, even if an internal function is called only once, it may serve to make the contract more readable. In such cases, consider the trade-off between gas efficiency and clarity.


Conclusion: Inlining single-use internal functions can be an effective way to make smart contracts more gas-efficient. However, always weigh the benefits against the potential future needs of your contract and the clarity of your code.

๐Ÿ“š
๐ŸŒช๏ธ
Book an audit with Zokyo