diff options
| author | João Vítor <joaovmferreira@gmail.com> | 2018-05-28 08:58:58 +0800 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2018-05-28 08:58:58 +0800 |
| commit | 899bd5f39a6d078fb1acc43ec18d547f16d63532 (patch) | |
| tree | 71c2df023ac4ae1232a1d6a0b6630e46ee6e0f2a | |
| parent | f5f1bec75995c8e1025750df149c08e3287f7bcb (diff) | |
| download | dexon-solidity-899bd5f39a6d078fb1acc43ec18d547f16d63532.tar.gz dexon-solidity-899bd5f39a6d078fb1acc43ec18d547f16d63532.tar.zst dexon-solidity-899bd5f39a6d078fb1acc43ec18d547f16d63532.zip | |
clarify warnings in contracts.rst
closes #4117
| -rw-r--r-- | docs/contracts.rst | 5 |
1 files changed, 5 insertions, 0 deletions
diff --git a/docs/contracts.rst b/docs/contracts.rst index 00ef3fc6..7f1899fa 100644 --- a/docs/contracts.rst +++ b/docs/contracts.rst @@ -526,9 +526,14 @@ In addition to the list of state modifying statements explained above, the follo It is not possible to prevent functions from reading the state at the level of the EVM, it is only possible to prevent them from writing to the state (i.e. only ``view`` can be enforced at the EVM level, ``pure`` can not). + It is a non-circumventable runtime checks done by the EVM. .. warning:: Before version 0.4.17 the compiler didn't enforce that ``pure`` is not reading the state. + It is a compile-time type check, which can be circumvented doing invalid explicit conversions + between contract types, because the compiler can verify that the type of the contract does + not do state-changing operations, but it cannot check that the contract that will be called + at runtime is actually of that type. .. index:: ! fallback function, function;fallback |