diff options
| author | pierzchalski <e.a.pierzchalski@gmail.com> | 2016-04-15 13:13:55 +1000 |
|---|---|---|
| committer | pierzchalski <e.a.pierzchalski@gmail.com> | 2016-04-15 13:13:55 +1000 |
| commit | d95ca2822cdc67ddec96d16533e23a10d6bfd136 (patch) | |
| tree | 05012aec8cc1f37423ce57940b07bd8079a5aea3 /src/liballoc_system | |
| parent | d8d8669439bd9e636b9209733c24c32063cc611d (diff) | |
| download | rust-d95ca2822cdc67ddec96d16533e23a10d6bfd136.tar.gz rust-d95ca2822cdc67ddec96d16533e23a10d6bfd136.zip | |
Add tests against weird provided/required method behaviour
In `test/rustdoc/manual_impl.rs` there are now three structs: * S1 implements and documents required method `a_method`. * S2 implements and documents `a_method` as well as provided method `b_method`. * S3 implements `a_method` and `b_method`, but only documents `b_method`. For a struct, we want the rendered trait impls to include documentation if and only if it appears on the trait implementation itself (since users can just go to the trait definition for anything not covered in the impl docs). This means we expect: * S1, S2, and S3 to all include top-level trait impl docs. * S1, S2, and S3 to exclude all trait definition docs. * S1 to show impl docs for `a_method`. * S2 to show impl docs for `a_method` and `b_method`. * S3 to show impl docs for `b_method`. These tests cover those cases.
Diffstat (limited to 'src/liballoc_system')
0 files changed, 0 insertions, 0 deletions
