diff options
author | William Entriken <github.com@phor.net> | 2018-01-15 02:56:02 +0800 |
---|---|---|
committer | GitHub <noreply@github.com> | 2018-01-15 02:56:02 +0800 |
commit | b1d99587e08e60465aac30c749d9965018ff175f (patch) | |
tree | f3a27747dd2268314785d28a0c8b47f709920ac3 | |
parent | 0c20b6da6b6c5f8fa72c389648b5da54c13945f9 (diff) | |
download | dexon-solidity-b1d99587e08e60465aac30c749d9965018ff175f.tar.gz dexon-solidity-b1d99587e08e60465aac30c749d9965018ff175f.tar.zst dexon-solidity-b1d99587e08e60465aac30c749d9965018ff175f.zip |
Use CapWords style for example
Follows recommendation in https://github.com/ethereum/solidity/pull/3392
-rw-r--r-- | docs/frequently-asked-questions.rst | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/docs/frequently-asked-questions.rst b/docs/frequently-asked-questions.rst index 5343b848..7c934041 100644 --- a/docs/frequently-asked-questions.rst +++ b/docs/frequently-asked-questions.rst @@ -433,14 +433,14 @@ What happens to a ``struct``'s mapping when copying over a ``struct``? This is a very interesting question. Suppose that we have a contract field set up like such:: - struct user { + struct User { mapping(string => string) comments; } function somefunction public { - user user1; + User user1; user1.comments["Hello"] = "World"; - user user2 = user1; + User user2 = user1; } In this case, the mapping of the struct being copied over into the userList is ignored as there is no "list of mapped keys". |