aboutsummaryrefslogtreecommitdiffstats
path: root/docs
diff options
context:
space:
mode:
authorchriseth <chris@ethereum.org>2018-01-15 17:55:11 +0800
committerGitHub <noreply@github.com>2018-01-15 17:55:11 +0800
commit14fcbd659fcdadf6c4314bdfcfbbe65fbc792c4a (patch)
tree6a3591aff2bb9480611f90a4f544d8680b0c55c7 /docs
parente6d15cd01efc252da1205f36b6e7ab7230f642f8 (diff)
parentb1d99587e08e60465aac30c749d9965018ff175f (diff)
downloaddexon-solidity-14fcbd659fcdadf6c4314bdfcfbbe65fbc792c4a.tar.gz
dexon-solidity-14fcbd659fcdadf6c4314bdfcfbbe65fbc792c4a.tar.zst
dexon-solidity-14fcbd659fcdadf6c4314bdfcfbbe65fbc792c4a.zip
Merge pull request #3393 from fulldecent/patch-5
Use CapWords style for example
Diffstat (limited to 'docs')
-rw-r--r--docs/frequently-asked-questions.rst6
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".