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

Update types.rst

Browse Source
This commit is contained in:
James Ray 2017-07-01 13:31:31 +10:00 committed by GitHub
parent 77e4f9c8fc
commit 3594f973df
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
docs/types.rst
View File

@ -557,7 +557,7 @@ So ``bytes`` should always be preferred over ``byte[]`` because it is cheaper.
that you are accessing the low-level bytes of the UTF-8 representation, that you are accessing the low-level bytes of the UTF-8 representation,
and not the individual characters! and not the individual characters!
It is possible to mark arrays ``public`` and have Solidity create a :ref:`getters <visibility-and-getters>`. It is possible to mark arrays ``public`` and have Solidity create a :ref:`getter <visibility-and-getters>`.
The numeric index will become a required parameter for the getter. The numeric index will become a required parameter for the getter.
.. index:: ! array;allocating, new .. index:: ! array;allocating, new
@ -806,7 +806,7 @@ Because of this, mappings do not have a length or a concept of a key or value be
Mappings are only allowed for state variables (or as storage reference types Mappings are only allowed for state variables (or as storage reference types
in internal functions). in internal functions).
It is possible to mark mappings ``public`` and have Solidity create a :ref:`getters <visibility-and-getters>`. It is possible to mark mappings ``public`` and have Solidity create a :ref:`getter <visibility-and-getters>`.
The ``_KeyType`` will become a required parameter for the getter and it will The ``_KeyType`` will become a required parameter for the getter and it will
return ``_ValueType``. return ``_ValueType``.