about summary refs log tree commit diff
path: root/src/test/incremental/thinlto
diff options
context:
space:
mode:
authorEduard-Mihai Burtescu <edy.burt@gmail.com>2016-11-12 10:38:37 +0200
committerGitHub <noreply@github.com>2016-11-12 10:38:37 +0200
commit66da9a291152feeedc9bb53f23f4577478b377e1 (patch)
tree966e49c53b4b0665f4c4fcde4e51a11a05ab5370 /src/test/incremental/thinlto
parent2db360eec1685a7bf33cf48ff9b9ab1757dcb358 (diff)
parent2a832a03c5a3efd6388e4eb5c5b5b4568bcd80f6 (diff)
downloadrust-66da9a291152feeedc9bb53f23f4577478b377e1.tar.gz
rust-66da9a291152feeedc9bb53f23f4577478b377e1.zip
Rollup merge of #37368 - trotter:patch-1, r=steveklabnik
Update testing.md to reflect changes to cargo new

`cargo new` now creates a `src/lib.rs` with a `tests` module by default. I've updated the earlier examples in this doc to reflect this. However, I don't know how we want to approach the "introduction" to idiomatic testing that follows in "the tests module" section. I _think_ it should be broken apart, with the module concept being introduced early on, and the `super` concept being addressed when we hit the `add_two` example. I'd like to get agreement on that being the right approach before I do it though.

I _also_ removed the `#fn main() {}` hidden at the beginning of each example, as these cause Rust Playground to not treat the file as a set of tests that it can run. Removing it _should_ cause Rust Playground to display a "Test >" button in the top left when a user runs the code, which will allow them to see the test runner output.
Diffstat (limited to 'src/test/incremental/thinlto')
0 files changed, 0 insertions, 0 deletions