ProvableHQ/leo
1
1
Fork 0
mirror of https://github.com/ProvableHQ/leo.git synced 2024-12-23 02:01:54 +03:00
Code Issues Packages Projects Releases Wiki Activity

[RFC] Incorporate naming suggestion.

Browse Source
This commit is contained in:
Alessandro Coglio 2021-09-20 09:55:50 -07:00
parent b08e63124b
commit 59cadadf2d
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/rfc/012-record-transaction-model.md
View File

@ -190,7 +190,7 @@ However, we probably want `input` to be read-only,
i.e. disallow assigning to an old record slot. i.e. disallow assigning to an old record slot.
Designating `input` as `const` does not seem right, Designating `input` as `const` does not seem right,
as that designation normally means that it is compiled into the circuit. as that designation normally means that it is compiled into the circuit.
Instead, we could provide read-only access via member function (e.g. `get_payload()`, `get_balance()`), Instead, we could provide read-only access via member function (e.g. `payload()`, `balance()`),
but we still have to prohibit assignments to member variables (which is currently allowed on any circuit type). but we still have to prohibit assignments to member variables (which is currently allowed on any circuit type).
As an orthogonal and more generally useful feature, As an orthogonal and more generally useful feature,
we could consider adding public/private access designations to Leo circuit members. we could consider adding public/private access designations to Leo circuit members.