mirror of
https://github.com/ethereum/solidity
synced 2023-10-03 13:03:40 +00:00
Document byte[] vs bytes
This commit is contained in:
parent
8743b2cead
commit
f787ecae5a
@ -441,13 +441,6 @@ The correct way to do this is the following::
|
||||
}
|
||||
}
|
||||
|
||||
What is the difference between ``bytes`` and ``byte[]``?
|
||||
========================================================
|
||||
|
||||
``bytes`` is usually more efficient: When used as arguments to functions (i.e. in
|
||||
CALLDATA) or in memory, every single element of a ``byte[]`` is padded to 32
|
||||
bytes which wastes 31 bytes per element.
|
||||
|
||||
Is it possible to send a value while calling an overloaded function?
|
||||
====================================================================
|
||||
|
||||
|
@ -181,6 +181,10 @@ Members:
|
||||
|
||||
* ``.length`` yields the fixed length of the byte array (read-only).
|
||||
|
||||
.. note::
|
||||
It is possible to use an array of bytes as ``byte[]``, but it is wasting a lot of space, 31 bytes every element,
|
||||
to be exact, when passing in calls. It is better to use ``bytes``.
|
||||
|
||||
Dynamically-sized byte array
|
||||
----------------------------
|
||||
|
||||
|
Loading…
Reference in New Issue
Block a user