Skip to content

Commit b787c32

Browse files
Dev-Doggocameel
authored andcommitted
Update receive function documentation
The receive function documentation is slightly inaccurate currently, as a contract can still receive Ether through payable functions even if no receive or payable fallback function is present.
1 parent ce18ddd commit b787c32

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

docs/contracts/functions.rst

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -297,7 +297,7 @@ on plain Ether transfers (e.g. via ``.send()`` or ``.transfer()``). If no such
297297
function exists, but a payable :ref:`fallback function <fallback-function>`
298298
exists, the fallback function will be called on a plain Ether transfer. If
299299
neither a receive Ether nor a payable fallback function is present, the
300-
contract cannot receive Ether through regular transactions and throws an
300+
contract cannot receive Ether through a transaction that does not represent a payable function call and throws an
301301
exception.
302302

303303
In the worst case, the ``receive`` function can only rely on 2300 gas being

0 commit comments

Comments
 (0)