mirror of
https://github.com/ethereum/solidity
synced 2023-10-03 13:03:40 +00:00
86 lines
3.2 KiB
ReStructuredText
86 lines
3.2 KiB
ReStructuredText
.. index:: type
|
|
|
|
.. _types:
|
|
|
|
*****
|
|
Types
|
|
*****
|
|
|
|
Solidity is a statically typed language, which means that the type of each
|
|
variable (state and local) needs to be specified.
|
|
Solidity provides several elementary types which can be combined to form complex types.
|
|
|
|
In addition, types can interact with each other in expressions containing
|
|
operators. For a quick reference of the various operators, see :ref:`order`.
|
|
|
|
The concept of "undefined" or "null" values does not exist in Solidity, but newly
|
|
declared variables always have a :ref:`default value<default-value>` dependent
|
|
on its type. To handle any unexpected values, you should use the :ref:`revert function<assert-and-require>` to revert the whole transaction, or return a
|
|
tuple with a second `bool` value denoting success.
|
|
|
|
.. include:: types/value-types.rst
|
|
|
|
.. include:: types/reference-types.rst
|
|
|
|
.. index:: !mapping
|
|
.. _mapping-types:
|
|
|
|
Mapping Types
|
|
=============
|
|
|
|
You declare mapping types with the syntax ``mapping(_KeyType => _ValueType)``.
|
|
The ``_KeyType`` can be any elementary type. This means it can be any of
|
|
the built-in value types plus ``bytes`` and ``string``. User-defined
|
|
or complex types like contract types, enums, mappings, structs and any array type
|
|
apart from ``bytes`` and ``string`` are not allowed.
|
|
``_ValueType`` can be any type, including mappings.
|
|
|
|
You can think of mappings as `hash tables <https://en.wikipedia.org/wiki/Hash_table>`_, which are virtually initialised
|
|
such that every possible key exists and is mapped to a value whose
|
|
byte-representation is all zeros, a type's :ref:`default value <default-value>`. The similarity ends there, the key data is not stored in a
|
|
mapping, only its ``keccak256`` hash is used to look up the value.
|
|
|
|
Because of this, mappings do not have a length or a concept of a key or
|
|
value being set.
|
|
|
|
Mappings can only have a data location of ``storage`` and thus
|
|
are allowed for state variables, as storage reference types
|
|
in functions, or as parameters for library functions.
|
|
They cannot be used as parameters or return parameters
|
|
of contract functions that are publicly visible.
|
|
|
|
You can mark variables of mapping type as ``public`` and Solidity creates a
|
|
:ref:`getter <visibility-and-getters>` for you. The ``_KeyType`` becomes a
|
|
parameter for the getter. If ``_ValueType`` is a value type or a struct,
|
|
the getter returns ``_ValueType``.
|
|
If ``_ValueType`` is an array or a mapping, the getter has one parameter for
|
|
each ``_KeyType``, recursively. For example with a mapping:
|
|
|
|
::
|
|
|
|
pragma solidity >=0.4.0 <0.6.0;
|
|
|
|
contract MappingExample {
|
|
mapping(address => uint) public balances;
|
|
|
|
function update(uint newBalance) public {
|
|
balances[msg.sender] = newBalance;
|
|
}
|
|
}
|
|
|
|
contract MappingUser {
|
|
function f() public returns (uint) {
|
|
MappingExample m = new MappingExample();
|
|
m.update(100);
|
|
return m.balances(address(this));
|
|
}
|
|
}
|
|
|
|
|
|
.. note::
|
|
Mappings are not iterable, but it is possible to implement a data structure
|
|
on top of them. For an example, see `iterable mapping <https://github.com/ethereum/dapp-bin/blob/master/library/iterable_mapping.sol>`_.
|
|
|
|
.. include:: types/operators.rst
|
|
|
|
.. include:: types/conversion.rst |