Out of gas on deployment: should a low-traffic contract trade revert reason strings for custom errors?
I am finalizing a small Solidity contract that will be deployed once and called only occasionally, so the dominant cost is deployment rather than per-call execution. Since an out-of-gas failure consumes all supplied gas while reverting state, I want the deployed bytecode as small as reasonably possible before I commit to a compiler configuration. The documen
solidity