about summary refs log tree commit diff
path: root/src/test/rustdoc/check-source-code-urls-to-def-std.rs
diff options
context:
space:
mode:
authorbors <bors@rust-lang.org>2023-01-11 11:17:22 +0000
committerbors <bors@rust-lang.org>2023-01-11 11:17:22 +0000
commitb22c152958eade17a71d899b29a2d39bcc77aa48 (patch)
treeec6da75dc598a0a4086c0cc032c86d7241be1bc1 /src/test/rustdoc/check-source-code-urls-to-def-std.rs
parent8ecaad85f61375b18e1667b51a3ef350121d2ca0 (diff)
parent40ba0e84d53f605ccf01836e9c2d27892728ae81 (diff)
downloadrust-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/check-source-code-urls-to-def-std.rs')
-rw-r--r--src/test/rustdoc/check-source-code-urls-to-def-std.rs42
1 files changed, 0 insertions, 42 deletions
diff --git a/src/test/rustdoc/check-source-code-urls-to-def-std.rs b/src/test/rustdoc/check-source-code-urls-to-def-std.rs
deleted file mode 100644
index e12d8445f4f..00000000000
--- a/src/test/rustdoc/check-source-code-urls-to-def-std.rs
+++ /dev/null
@@ -1,42 +0,0 @@
-// compile-flags: -Zunstable-options --generate-link-to-definition
-
-#![crate_name = "foo"]
-
-// @has 'src/foo/check-source-code-urls-to-def-std.rs.html'
-
-fn babar() {}
-
-// @has - '//a[@href="{{channel}}/std/primitive.u32.html"]' 'u32'
-// @has - '//a[@href="{{channel}}/std/primitive.str.html"]' 'str'
-// @has - '//a[@href="{{channel}}/std/primitive.bool.html"]' 'bool'
-// @has - '//a[@href="#7"]' 'babar'
-pub fn foo(a: u32, b: &str, c: String) {
-    let x = 12;
-    let y: bool = true;
-    babar();
-}
-
-macro_rules! yolo { () => {}}
-
-fn bar(a: i32) {}
-
-macro_rules! bar {
-    ($a:ident) => { bar($a) }
-}
-
-macro_rules! data {
-    ($x:expr) => { $x * 2 }
-}
-
-pub fn another_foo() {
-    // This is known limitation: if the macro doesn't generate anything, the visitor
-    // can't find any item or anything that could tell us that it comes from expansion.
-    // @!has - '//a[@href="#19"]' 'yolo!'
-    yolo!();
-    // @has - '//a[@href="{{channel}}/std/macro.eprintln.html"]' 'eprintln!'
-    eprintln!();
-    // @has - '//a[@href="#27-29"]' 'data!'
-    let x = data!(4);
-    // @has - '//a[@href="#23-25"]' 'bar!'
-    bar!(x);
-}