aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorritzdorf <hubert@chainsecurity.com>2018-11-13 22:54:13 +0800
committerGitHub <noreply@github.com>2018-11-13 22:54:13 +0800
commit8258712771164da6d365f2417eeb968045522a6f (patch)
tree486c30b7c725274edbe59c3755dd1035b169198e
parentc237013911aa5bb6102e1262e6aa62178c0f02e0 (diff)
downloaddexon-solidity-8258712771164da6d365f2417eeb968045522a6f.tar.gz
dexon-solidity-8258712771164da6d365f2417eeb968045522a6f.tar.zst
dexon-solidity-8258712771164da6d365f2417eeb968045522a6f.zip
keccak256 does not call an external contract
``keccak256`` will be compiled to the ``SHA3`` opcode and not call an external contract.
-rw-r--r--docs/contracts.rst2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/contracts.rst b/docs/contracts.rst
index 4d439b26..c1c51e56 100644
--- a/docs/contracts.rst
+++ b/docs/contracts.rst
@@ -455,7 +455,7 @@ execution data (``msg.value`` or ``gasleft()``) or makes calls to external contr
that might have a side-effect on memory allocation are allowed, but those that
might have a side-effect on other memory objects are not. The built-in functions
``keccak256``, ``sha256``, ``ripemd160``, ``ecrecover``, ``addmod`` and ``mulmod``
-are allowed (even though they do call external contracts).
+are allowed (even though, with the exception of ``keccak256``, they do call external contracts).
The reason behind allowing side-effects on the memory allocator is that it
should be possible to construct complex objects like e.g. lookup-tables.