cerc-io/solidity
10
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

Integers cannot be implicitly converted to address

Browse Source
This commit is contained in:
chriseth 2018-11-05 06:50:45 +01:00
parent e4da724fb8
commit 5df83346f3
1 changed files with 1 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
docs/types.rst
View File

@ -1225,7 +1225,6 @@ is possible if it
makes sense semantically and no information is lost: ``uint8`` is convertible to makes sense semantically and no information is lost: ``uint8`` is convertible to
``uint16`` and ``int128`` to ``int256``, but ``int8`` is not convertible to ``uint256`` ``uint16`` and ``int128`` to ``int256``, but ``int8`` is not convertible to ``uint256``
(because ``uint256`` cannot hold e.g. ``-1``). (because ``uint256`` cannot hold e.g. ``-1``).
Any integer type that can be converted to ``uint160`` can also be converted to ``address``.
For more details, please consult the sections about the types themselves. For more details, please consult the sections about the types themselves.
@ -1335,4 +1334,4 @@ Addresses
As described in :ref:`address_literals`, hex literals of the correct size that pass the checksum As described in :ref:`address_literals`, hex literals of the correct size that pass the checksum
test are of ``address`` type. No other literals can be implicitly converted to the ``address`` type. test are of ``address`` type. No other literals can be implicitly converted to the ``address`` type.
Explicit conversions from ``bytes20`` or any integer type to ``address`` results in ``address payable``. Explicit conversions from ``bytes20`` or any integer type to ``address`` result in ``address payable``.