-
Notifications
You must be signed in to change notification settings - Fork 6.1k
Change terminology used for input output parameters pt 2 #5324
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
docs/assembly.rst
Outdated
@@ -291,10 +291,10 @@ In the grammar, opcodes are represented as pre-defined identifiers. | |||
| | | | 8 byte value, ``this`` is the current contract's address | | |||
| | | | as a 20 byte value and ``s`` is a big-endian 256-bit value | | |||
+-------------------------+-----+---+-----------------------------------------------------------------+ | |||
| call(g, a, v, in, | | F | call contract at address a with input mem[in...(in+insize)) | |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think we should call these "function parameters", because we do not call a function. I would leave it as it is.
docs/layout-of-source-files.rst
Outdated
@@ -276,7 +276,7 @@ functions, annotate conditions for formal verification, and provide a | |||
function. | |||
|
|||
In the following example we document the title of the contract, the explanation | |||
for the two input parameters and two returned values. | |||
for the two function parameters and two return types. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
types
does not seem right here. I think we should either say return parameters
or return values
(which is slightly wrong, but perhaps better to understand).
docs/types.rst
Outdated
@@ -253,7 +253,7 @@ Send is the low-level counterpart of ``transfer``. If the execution fails, the c | |||
In order to interface with contracts that do not adhere to the ABI, | |||
or to get more direct control over the encoding, | |||
the functions ``call``, ``delegatecall`` and ``staticcall`` are provided. | |||
They all take a single ``bytes memory`` argument as input and | |||
They all take a single ``bytes memory`` function parameter and |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
They all take a single ``bytes memory`` function parameter and | |
They all take a single ``bytes memory`` parameter and |
("function" is implied)
3b1a43a
to
f30bd92
Compare
Codecov Report
@@ Coverage Diff @@
## develop #5324 +/- ##
==========================================
Coverage ? 87.99%
==========================================
Files ? 320
Lines ? 32444
Branches ? 3858
==========================================
Hits ? 28549
Misses ? 2590
Partials ? 1305
|
f30bd92
to
afdc82f
Compare
afdc82f
to
fa1cb34
Compare
Checklist
Description
As discussed here #4859 (comment) this first PR changes the terminology previously used for input and output parameters. Hopefully, I got the semantics, explanations and usage correct. Part 1 is here #5323.