diff options
author | Alex Beregszaszi <alex@rtfs.hu> | 2017-03-16 08:43:25 +0800 |
---|---|---|
committer | Alex Beregszaszi <alex@rtfs.hu> | 2017-03-16 08:43:30 +0800 |
commit | 42f2623cd3650437860604b7bb7117037416e1bb (patch) | |
tree | fa94f72830a1dcfd0199a7281e8629c043b5a8ee /docs/control-structures.rst | |
parent | 4c34adb799c4a4e6685e1ded414053604aa9a1d1 (diff) | |
download | dexon-solidity-42f2623cd3650437860604b7bb7117037416e1bb.tar.gz dexon-solidity-42f2623cd3650437860604b7bb7117037416e1bb.tar.zst dexon-solidity-42f2623cd3650437860604b7bb7117037416e1bb.zip |
Fix list indentation
Diffstat (limited to 'docs/control-structures.rst')
-rw-r--r-- | docs/control-structures.rst | 3 |
1 files changed, 2 insertions, 1 deletions
diff --git a/docs/control-structures.rst b/docs/control-structures.rst index 25bf203b..a3af41dd 100644 --- a/docs/control-structures.rst +++ b/docs/control-structures.rst @@ -399,6 +399,7 @@ Currently, Solidity automatically generates a runtime exception in the following #. If you call ``assert`` with an argument that evaluates to false. While a user-provided exception is generated in the following situations: + #. Calling ``throw``. #. Calling ``require`` with an argument that evaluates to ``false``. @@ -411,4 +412,4 @@ did not occur. Because we want to retain the atomicity of transactions, the safe If contracts are written so that ``assert`` is only used to test internal conditions and ``require`` is used in case of malformed input, a formal analysis tool that verifies that the invalid -opcode can never be reached can be used to check for the absence of errors assuming valid inputs.
\ No newline at end of file +opcode can never be reached can be used to check for the absence of errors assuming valid inputs. |