From 5df83346f36f7da62d914b8f4fc7036176292366 Mon Sep 17 00:00:00 2001 From: chriseth Date: Mon, 5 Nov 2018 06:50:45 +0100 Subject: Integers cannot be implicitly converted to address --- docs/types.rst | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) (limited to 'docs/types.rst') diff --git a/docs/types.rst b/docs/types.rst index bd5d1734..34b94b88 100644 --- a/docs/types.rst +++ b/docs/types.rst @@ -1225,7 +1225,6 @@ is possible if it makes sense semantically and no information is lost: ``uint8`` is convertible to ``uint16`` and ``int128`` to ``int256``, but ``int8`` is not convertible to ``uint256`` (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. @@ -1335,4 +1334,4 @@ Addresses 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. -Explicit conversions from ``bytes20`` or any integer type to ``address`` results in ``address payable``. \ No newline at end of file +Explicit conversions from ``bytes20`` or any integer type to ``address`` result in ``address payable``. -- cgit