diff options
| author | bors <bors@rust-lang.org> | 2023-01-11 11:17:22 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2023-01-11 11:17:22 +0000 |
| commit | b22c152958eade17a71d899b29a2d39bcc77aa48 (patch) | |
| tree | ec6da75dc598a0a4086c0cc032c86d7241be1bc1 /src/test/rustdoc-ui/coverage/enums.rs | |
| parent | 8ecaad85f61375b18e1667b51a3ef350121d2ca0 (diff) | |
| parent | 40ba0e84d53f605ccf01836e9c2d27892728ae81 (diff) | |
| download | rust-b22c152958eade17a71d899b29a2d39bcc77aa48.tar.gz rust-b22c152958eade17a71d899b29a2d39bcc77aa48.zip | |
Auto merge of #106458 - albertlarsan68:move-tests, r=jyn514
Move src/test to the root
See MCP at rust-lang/compiler-team#573
There may be more changes needed.
The first commit is just the move of the files:
You can check that the first commit did not do anything else than renames by running
```
git diff --diff-filter=r -M100% <rust-lang remote>/master <first commit hash>
```
The output should be empty, because the filter excludes renames, and the match threshold for qualifying a rename is 100%.
The second one is mostly a "find and replace" of `src/test` to `tests` and whatever is needed to make CI pass.
What is left to do:
---
- [x] Move directory
- [ ] Change references to `src/test`
- [x] Change references in-tree
- [ ] Change references in submodules / out-of-tree docs
- [x] Make CI pass:
- [x] Fix tidy
- [x] Fix tests
- [x] Bless tests if needed (shouldn't normally)
- [ ] Merge it !
Diffstat (limited to 'src/test/rustdoc-ui/coverage/enums.rs')
| -rw-r--r-- | src/test/rustdoc-ui/coverage/enums.rs | 22 |
1 files changed, 0 insertions, 22 deletions
diff --git a/src/test/rustdoc-ui/coverage/enums.rs b/src/test/rustdoc-ui/coverage/enums.rs deleted file mode 100644 index a4ae36d6837..00000000000 --- a/src/test/rustdoc-ui/coverage/enums.rs +++ /dev/null @@ -1,22 +0,0 @@ -// compile-flags:-Z unstable-options --show-coverage -// check-pass - -//! (remember the crate root is still a module) - -/// so check out this enum here -pub enum ThisEnum { - /// this variant has some weird stuff going on - VarOne { - /// like, it has some named fields inside - field_one: usize, - // (these show up as struct fields) - field_two: usize, - }, - /// here's another variant for you - VarTwo(String), - // but not all of them need to be documented as thoroughly - VarThree, -} - -/// uninhabited enums? sure, let's throw one of those around -pub enum OtherEnum {} |
