about summary refs log tree commit diff
path: root/src/rustllvm/RustWrapper.cpp
diff options
context:
space:
mode:
authorSteve Klabnik <steve@steveklabnik.com>2015-07-29 10:30:33 -0400
committerSteve Klabnik <steve@steveklabnik.com>2015-07-29 10:30:33 -0400
commit10387d6839752ac6a8cd937b5f3fbd6a94c58f69 (patch)
treed770dcc73e4bc919963e34f676d84b7d595cb5f6 /src/rustllvm/RustWrapper.cpp
parente6ed27bc24852a9facbf87eb20f9462d88c70bbf (diff)
parent95c7f306c7c57f028d7e577ef13a5fc66f3086eb (diff)
downloadrust-10387d6839752ac6a8cd937b5f3fbd6a94c58f69.tar.gz
rust-10387d6839752ac6a8cd937b5f3fbd6a94c58f69.zip
Rollup merge of #27286 - lastorset:pub, r=steveklabnik
The reader could probably infer this from the current text, but for C++ programmers it's not obvious that struct fields don't automatically become public.

Apparently I wasn't the only one to be confused:

http://stackoverflow.com/questions/29157300/field-of-struct-is-private-when-importing-module

I don't think an example is necessary, but can add one if desired.

r? @steveklabnik 
Diffstat (limited to 'src/rustllvm/RustWrapper.cpp')
0 files changed, 0 insertions, 0 deletions