diff options
| author | bors <bors@rust-lang.org> | 2014-05-07 22:01:37 -0700 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2014-05-07 22:01:37 -0700 |
| commit | 26632d541c3f548b064ffea57f0cb2057b48f947 (patch) | |
| tree | af2e71bd60eaa1f9d1356c40d465d935260b1b52 /src/test/codegen/stack-alloc-string-slice.cc | |
| parent | e0fcb4eb3d516017c7c2fa8d17e7b8b82bdc065b (diff) | |
| parent | a22413b46aa57ed22e59a9c0e4d581d1eabfe2b2 (diff) | |
| download | rust-26632d541c3f548b064ffea57f0cb2057b48f947.tar.gz rust-26632d541c3f548b064ffea57f0cb2057b48f947.zip | |
auto merge of #13976 : pnkfelix/rust/fsk-fix-13965, r=alexcrichton
Fix #13965. This commit adopts the second strategy I outlined in #13965, where the bulk of the code is still "smoke tested" (in the sense that rustdoc attempts to run it, sending all of the generated output into a locally allocated `MemWriter`). The part of the code that is ignored (but included in the presentation) is isolated to a three-line `main` function that invokes the core rendering routine. In the generated rustdoc output, this leads to a small break between the two code blocks, but I do not think this is a large issue.
Diffstat (limited to 'src/test/codegen/stack-alloc-string-slice.cc')
0 files changed, 0 insertions, 0 deletions