diff options
| author | bors <bors@rust-lang.org> | 2014-07-18 01:46:24 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2014-07-18 01:46:24 +0000 |
| commit | cebed8ab921e7e5f539236ae7ef87ee1992eaaaf (patch) | |
| tree | c11ee3b55c11e726493a8d447629d15e8446bdab /src/rustllvm/ExecutionEngineWrapper.cpp | |
| parent | f50e4ee559c0e6253e9d46a8e6763e25f7b90d90 (diff) | |
| parent | 226b7d1b725300fe6fbcfc1a66dfc1298f0af893 (diff) | |
| download | rust-cebed8ab921e7e5f539236ae7ef87ee1992eaaaf.tar.gz rust-cebed8ab921e7e5f539236ae7ef87ee1992eaaaf.zip | |
auto merge of #15593 : steveklabnik/rust/string_guide, r=kballard
I decided to change it up a little today and hack out the beginning of the String guide. Strings are different enough in Rust that I think they deserve a specific guide, especially for those who are used to managed languages. I decided to start with Strings because they get asked about a lot in IRC, and also based on discussions like this one on reddit: http://www.reddit.com/r/rust/comments/2ac390/generic_string_literals/ I blatantly stole bits from our other documentation on Strings. It's a little sparse at current, but I wanted to start somewhere. I am not exactly sure what should go in "Best Practices," and would like the feedback from the team on this. Specifically due to comments like this one: http://www.reddit.com/r/rust/comments/2ac390/generic_string_literals/citmxb5
Diffstat (limited to 'src/rustllvm/ExecutionEngineWrapper.cpp')
0 files changed, 0 insertions, 0 deletions
