mirror of
https://github.com/ethereum/solidity
synced 2023-10-03 13:03:40 +00:00
fixes ethereum/solidity#1209
This clears up a common and easy misunderstanding which seems to occur rather often. (https://ethereum.stackexchange.com/questions/8263/trying-to-understand-libraries)
This commit is contained in:
parent
e7afde9587
commit
b4fb7255dd
@ -1115,7 +1115,7 @@ if the library were a base contract. Of course, calls to internal functions
|
|||||||
use the internal calling convention, which means that all internal types
|
use the internal calling convention, which means that all internal types
|
||||||
can be passed and memory types will be passed by reference and not copied.
|
can be passed and memory types will be passed by reference and not copied.
|
||||||
To realize this in the EVM, code of internal library functions
|
To realize this in the EVM, code of internal library functions
|
||||||
and all functions called from therein will be pulled into the calling
|
and all functions called from therein will at compile time be pulled into the calling
|
||||||
contract, and a regular ``JUMP`` call will be used instead of a ``DELEGATECALL``.
|
contract, and a regular ``JUMP`` call will be used instead of a ``DELEGATECALL``.
|
||||||
|
|
||||||
.. index:: using for, set
|
.. index:: using for, set
|
||||||
|
Loading…
Reference in New Issue
Block a user