cerc-io/solidity
16
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

Clarify ABI & Solidity types

Browse Source
This commit is contained in:
Alex Beregszaszi 2017-09-11 15:03:49 +01:00
parent c5063d3155
commit 923373b41e
1 changed files with 5 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
docs/abi-spec.rst
View File

@ -75,6 +75,9 @@ of them inside parentheses, separated by commas:
It is possible to form tuples of tuples, arrays of tuples and so on. It is possible to form tuples of tuples, arrays of tuples and so on.
.. note::
Solidity supports all the types presented above with the same names with the exception of tuples. The ABI tuple type is utilised for encoding Solidity ``structs``.
Formal Specification of the Encoding Formal Specification of the Encoding
==================================== ====================================
@ -359,8 +362,8 @@ would result in the JSON:
Handling tuple types Handling tuple types
-------------------- --------------------
If tuples are part of the type, we still want to know the name of the components. Because of that, Despite that names are intentionally not part of the ABI encoding they do make a lot of sense to be included
the json structure gets arbitrarily nested in the following way: in the JSON to enable displaying it to the end user. The structure is nested in the following way:
An object with members ``name``, ``type`` and potentially ``components`` describes a typed variable. An object with members ``name``, ``type`` and potentially ``components`` describes a typed variable.
The canonical type is determined until a tuple type is reached and the string description up The canonical type is determined until a tuple type is reached and the string description up