cerc-io/solidity
16
0
Fork 0
mirror of https://github.com/ethereum/solidity synced 2023-10-03 13:03:40 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

Merge pull request #10093 from ethereum/clarifyEvaluation

Browse Source 
Clarify evaluation of arguments to require.
This commit is contained in:
chriseth 2020-10-23 10:41:46 +02:00 committed by GitHub
commit 08a27b9c5b
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 7 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
docs/control-structures.rst
View File

@ -615,7 +615,13 @@ The following example shows how to use an error string together with ``revert``
} }
} }
The two syntax options are equivalent, it's developer preference which to use. If you provide the reason string directly, then the two syntax options are equivalent, it is the developer's preference which one to use.
.. note::
The ``require`` function is evaluated just as any other function.
This means that all arguments are evaluated before the function itself is executed.
In particular, in ``require(condition, f())`` the function ``f`` is executed even if
``condition`` is true.
The provided string is :ref:`abi-encoded <ABI>` as if it were a call to a function ``Error(string)``. The provided string is :ref:`abi-encoded <ABI>` as if it were a call to a function ``Error(string)``.
In the above example, ``revert("Not enough Ether provided.");`` returns the following hexadecimal as error return data: In the above example, ``revert("Not enough Ether provided.");`` returns the following hexadecimal as error return data: