You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
= help: there is an attribute with a similar name: `compile_fail`
12
-
= help: the code block will either not be tested if not marked as a rust one or won't fail if it compiles successfully
11
+
= help: use `compile_fail` to invert the results of this test, so that it passes if it cannot be compiled and fails if it can
12
+
= help: this code block may be skipped during testing, because unknown attributes are treated as markers for code samples written in other programming languages, unless it is also explicitly marked as `rust`
= help: there is an attribute with a similar name: `compile_fail`
30
-
= help: the code block will either not be tested if not marked as a rust one or won't fail if it compiles successfully
29
+
= help: use `compile_fail` to invert the results of this test, so that it passes if it cannot be compiled and fails if it can
30
+
= help: this code block may be skipped during testing, because unknown attributes are treated as markers for code samples written in other programming languages, unless it is also explicitly marked as `rust`
= help: there is an attribute with a similar name: `compile_fail`
43
-
= help: the code block will either not be tested if not marked as a rust one or won't fail if it compiles successfully
42
+
= help: use `compile_fail` to invert the results of this test, so that it passes if it cannot be compiled and fails if it can
43
+
= help: this code block may be skipped during testing, because unknown attributes are treated as markers for code samples written in other programming languages, unless it is also explicitly marked as `rust`
= help: there is an attribute with a similar name: `should_panic`
56
-
= help: the code block will either not be tested if not marked as a rust one or won't fail if it doesn't panic when running
55
+
= help: use `should_panic` to invert the results of this test, so that if passes if it panics and fails if it does not
56
+
= help: this code block may be skipped during testing, because unknown attributes are treated as markers for code samples written in other programming languages, unless it is also explicitly marked as `rust`
= help: there is an attribute with a similar name: `should_panic`
69
-
= help: the code block will either not be tested if not marked as a rust one or won't fail if it doesn't panic when running
68
+
= help: use `should_panic` to invert the results of this test, so that if passes if it panics and fails if it does not
69
+
= help: this code block may be skipped during testing, because unknown attributes are treated as markers for code samples written in other programming languages, unless it is also explicitly marked as `rust`
= help: there is an attribute with a similar name: `should_panic`
82
-
= help: the code block will either not be tested if not marked as a rust one or won't fail if it doesn't panic when running
81
+
= help: use `should_panic` to invert the results of this test, so that if passes if it panics and fails if it does not
82
+
= help: this code block may be skipped during testing, because unknown attributes are treated as markers for code samples written in other programming languages, unless it is also explicitly marked as `rust`
= help: there is an attribute with a similar name: `no_run`
95
-
= help: the code block will either not be tested if not marked as a rust one or will be run (which you might not want)
94
+
= help: use `no_run` to compile, but not run, the code sample during testing
95
+
= help: this code block may be skipped during testing, because unknown attributes are treated as markers for code samples written in other programming languages, unless it is also explicitly marked as `rust`
= help: there is an attribute with a similar name: `no_run`
108
-
= help: the code block will either not be tested if not marked as a rust one or will be run (which you might not want)
107
+
= help: use `no_run` to compile, but not run, the code sample during testing
108
+
= help: this code block may be skipped during testing, because unknown attributes are treated as markers for code samples written in other programming languages, unless it is also explicitly marked as `rust`
= help: there is an attribute with a similar name: `no_run`
121
-
= help: the code block will either not be tested if not marked as a rust one or will be run (which you might not want)
120
+
= help: use `no_run` to compile, but not run, the code sample during testing
121
+
= help: this code block may be skipped during testing, because unknown attributes are treated as markers for code samples written in other programming languages, unless it is also explicitly marked as `rust`
= help: there is an attribute with a similar name: `test_harness`
134
-
= help: the code block will either not be tested if not marked as a rust one or the code will be wrapped inside a main function
133
+
= help: use `test_harness` to run functions marked `#[test]` instead of a potentially-implicit `main` function
134
+
= help: this code block may be skipped during testing, because unknown attributes are treated as markers for code samples written in other programming languages, unless it is also explicitly marked as `rust`
= help: there is an attribute with a similar name: `test_harness`
147
-
= help: the code block will either not be tested if not marked as a rust one or the code will be wrapped inside a main function
146
+
= help: use `test_harness` to run functions marked `#[test]` instead of a potentially-implicit `main` function
147
+
= help: this code block may be skipped during testing, because unknown attributes are treated as markers for code samples written in other programming languages, unless it is also explicitly marked as `rust`
= help: there is an attribute with a similar name: `test_harness`
160
-
= help: the code block will either not be tested if not marked as a rust one or the code will be wrapped inside a main function
159
+
= help: use `test_harness` to run functions marked `#[test]` instead of a potentially-implicit `main` function
160
+
= help: this code block may be skipped during testing, because unknown attributes are treated as markers for code samples written in other programming languages, unless it is also explicitly marked as `rust`
= help: there is an attribute with a similar name: `standalone-crate`
14
-
= help: the code block will either not be tested if not marked as a rust one or the code will be run as part of the merged doctests if compatible
13
+
= help: use `standalone-crate` to compile this code block separately
14
+
= help: this code block may be skipped during testing, because unknown attributes are treated as markers for code samples written in other programming languages, unless it is also explicitly marked as `rust`
= help: there is an attribute with a similar name: `standalone-crate`
35
-
= help: the code block will either not be tested if not marked as a rust one or the code will be run as part of the merged doctests if compatible
34
+
= help: use `standalone-crate` to compile this code block separately
35
+
= help: this code block may be skipped during testing, because unknown attributes are treated as markers for code samples written in other programming languages, unless it is also explicitly marked as `rust`
Copy file name to clipboardExpand all lines: tests/rustdoc-ui/lints/check-attr.stderr
+26-26Lines changed: 26 additions & 26 deletions
Original file line number
Diff line number
Diff line change
@@ -10,8 +10,8 @@ LL | | /// boo
10
10
LL | | /// ```
11
11
| |_______^
12
12
|
13
-
= help: there is an attribute with a similar name: `compile_fail`
14
-
= help: the code block will either not be tested if not marked as a rust one or won't fail if it compiles successfully
13
+
= help: use `compile_fail` to invert the results of this test, so that it passes if it cannot be compiled and fails if it can
14
+
= help: this code block may be skipped during testing, because unknown attributes are treated as markers for code samples written in other programming languages, unless it is also explicitly marked as `rust`
15
15
note: the lint level is defined here
16
16
--> $DIR/check-attr.rs:1:9
17
17
|
@@ -30,8 +30,8 @@ LL | | /// boo
30
30
LL | | /// ```
31
31
| |_______^
32
32
|
33
-
= help: there is an attribute with a similar name: `compile_fail`
34
-
= help: the code block will either not be tested if not marked as a rust one or won't fail if it compiles successfully
33
+
= help: use `compile_fail` to invert the results of this test, so that it passes if it cannot be compiled and fails if it can
34
+
= help: this code block may be skipped during testing, because unknown attributes are treated as markers for code samples written in other programming languages, unless it is also explicitly marked as `rust`
35
35
36
36
error: unknown attribute `comPile_fail`
37
37
--> $DIR/check-attr.rs:3:1
@@ -45,8 +45,8 @@ LL | | /// boo
45
45
LL | | /// ```
46
46
| |_______^
47
47
|
48
-
= help: there is an attribute with a similar name: `compile_fail`
49
-
= help: the code block will either not be tested if not marked as a rust one or won't fail if it compiles successfully
48
+
= help: use `compile_fail` to invert the results of this test, so that it passes if it cannot be compiled and fails if it can
49
+
= help: this code block may be skipped during testing, because unknown attributes are treated as markers for code samples written in other programming languages, unless it is also explicitly marked as `rust`
50
50
51
51
error: unknown attribute `should-panic`
52
52
--> $DIR/check-attr.rs:13:1
@@ -60,8 +60,8 @@ LL | | /// boo
60
60
LL | | /// ```
61
61
| |_______^
62
62
|
63
-
= help: there is an attribute with a similar name: `should_panic`
64
-
= help: the code block will either not be tested if not marked as a rust one or won't fail if it doesn't panic when running
63
+
= help: use `should_panic` to invert the results of this test, so that if passes if it panics and fails if it does not
64
+
= help: this code block may be skipped during testing, because unknown attributes are treated as markers for code samples written in other programming languages, unless it is also explicitly marked as `rust`
65
65
66
66
error: unknown attribute `shouldpanic`
67
67
--> $DIR/check-attr.rs:13:1
@@ -75,8 +75,8 @@ LL | | /// boo
75
75
LL | | /// ```
76
76
| |_______^
77
77
|
78
-
= help: there is an attribute with a similar name: `should_panic`
79
-
= help: the code block will either not be tested if not marked as a rust one or won't fail if it doesn't panic when running
78
+
= help: use `should_panic` to invert the results of this test, so that if passes if it panics and fails if it does not
79
+
= help: this code block may be skipped during testing, because unknown attributes are treated as markers for code samples written in other programming languages, unless it is also explicitly marked as `rust`
80
80
81
81
error: unknown attribute `sHould_panic`
82
82
--> $DIR/check-attr.rs:13:1
@@ -90,8 +90,8 @@ LL | | /// boo
90
90
LL | | /// ```
91
91
| |_______^
92
92
|
93
-
= help: there is an attribute with a similar name: `should_panic`
94
-
= help: the code block will either not be tested if not marked as a rust one or won't fail if it doesn't panic when running
93
+
= help: use `should_panic` to invert the results of this test, so that if passes if it panics and fails if it does not
94
+
= help: this code block may be skipped during testing, because unknown attributes are treated as markers for code samples written in other programming languages, unless it is also explicitly marked as `rust`
95
95
96
96
error: unknown attribute `no-run`
97
97
--> $DIR/check-attr.rs:23:1
@@ -105,8 +105,8 @@ LL | | /// boo
105
105
LL | | /// ```
106
106
| |_______^
107
107
|
108
-
= help: there is an attribute with a similar name: `no_run`
109
-
= help: the code block will either not be tested if not marked as a rust one or will be run (which you might not want)
108
+
= help: use `no_run` to compile, but not run, the code sample during testing
109
+
= help: this code block may be skipped during testing, because unknown attributes are treated as markers for code samples written in other programming languages, unless it is also explicitly marked as `rust`
110
110
111
111
error: unknown attribute `norun`
112
112
--> $DIR/check-attr.rs:23:1
@@ -120,8 +120,8 @@ LL | | /// boo
120
120
LL | | /// ```
121
121
| |_______^
122
122
|
123
-
= help: there is an attribute with a similar name: `no_run`
124
-
= help: the code block will either not be tested if not marked as a rust one or will be run (which you might not want)
123
+
= help: use `no_run` to compile, but not run, the code sample during testing
124
+
= help: this code block may be skipped during testing, because unknown attributes are treated as markers for code samples written in other programming languages, unless it is also explicitly marked as `rust`
125
125
126
126
error: unknown attribute `no_Run`
127
127
--> $DIR/check-attr.rs:23:1
@@ -135,8 +135,8 @@ LL | | /// boo
135
135
LL | | /// ```
136
136
| |_______^
137
137
|
138
-
= help: there is an attribute with a similar name: `no_run`
139
-
= help: the code block will either not be tested if not marked as a rust one or will be run (which you might not want)
138
+
= help: use `no_run` to compile, but not run, the code sample during testing
139
+
= help: this code block may be skipped during testing, because unknown attributes are treated as markers for code samples written in other programming languages, unless it is also explicitly marked as `rust`
140
140
141
141
error: unknown attribute `test-harness`
142
142
--> $DIR/check-attr.rs:33:1
@@ -150,8 +150,8 @@ LL | | /// boo
150
150
LL | | /// ```
151
151
| |_______^
152
152
|
153
-
= help: there is an attribute with a similar name: `test_harness`
154
-
= help: the code block will either not be tested if not marked as a rust one or the code will be wrapped inside a main function
153
+
= help: use `test_harness` to run functions marked `#[test]` instead of a potentially-implicit `main` function
154
+
= help: this code block may be skipped during testing, because unknown attributes are treated as markers for code samples written in other programming languages, unless it is also explicitly marked as `rust`
155
155
156
156
error: unknown attribute `testharness`
157
157
--> $DIR/check-attr.rs:33:1
@@ -165,8 +165,8 @@ LL | | /// boo
165
165
LL | | /// ```
166
166
| |_______^
167
167
|
168
-
= help: there is an attribute with a similar name: `test_harness`
169
-
= help: the code block will either not be tested if not marked as a rust one or the code will be wrapped inside a main function
168
+
= help: use `test_harness` to run functions marked `#[test]` instead of a potentially-implicit `main` function
169
+
= help: this code block may be skipped during testing, because unknown attributes are treated as markers for code samples written in other programming languages, unless it is also explicitly marked as `rust`
170
170
171
171
error: unknown attribute `teSt_harness`
172
172
--> $DIR/check-attr.rs:33:1
@@ -180,8 +180,8 @@ LL | | /// boo
180
180
LL | | /// ```
181
181
| |_______^
182
182
|
183
-
= help: there is an attribute with a similar name: `test_harness`
184
-
= help: the code block will either not be tested if not marked as a rust one or the code will be wrapped inside a main function
183
+
= help: use `test_harness` to run functions marked `#[test]` instead of a potentially-implicit `main` function
184
+
= help: this code block may be skipped during testing, because unknown attributes are treated as markers for code samples written in other programming languages, unless it is also explicitly marked as `rust`
185
185
186
186
error: unknown attribute `rust2018`
187
187
--> $DIR/check-attr.rs:43:1
@@ -222,8 +222,8 @@ LL | | /// boo
222
222
LL | | /// ```
223
223
| |_______^
224
224
|
225
-
= help: there is an attribute with a similar name: `should_panic`
226
-
= help: the code block will either not be tested if not marked as a rust one or won't fail if it doesn't panic when running
225
+
= help: use `should_panic` to invert the results of this test, so that if passes if it panics and fails if it does not
226
+
= help: this code block may be skipped during testing, because unknown attributes are treated as markers for code samples written in other programming languages, unless it is also explicitly marked as `rust`
Copy file name to clipboardExpand all lines: tests/rustdoc-ui/lints/check-fail.stderr
+4-4Lines changed: 4 additions & 4 deletions
Original file line number
Diff line number
Diff line change
@@ -31,8 +31,8 @@ LL | | //! let x = 12;
31
31
LL | | //! ```
32
32
| |_______^
33
33
|
34
-
= help: there is an attribute with a similar name: `test_harness`
35
-
= help: the code block will either not be tested if not marked as a rust one or the code will be wrapped inside a main function
34
+
= help: use `test_harness` to run functions marked `#[test]` instead of a potentially-implicit `main` function
35
+
= help: this code block may be skipped during testing, because unknown attributes are treated as markers for code samples written in other programming languages, unless it is also explicitly marked as `rust`
36
36
note: the lint level is defined here
37
37
--> $DIR/check-fail.rs:6:9
38
38
|
@@ -51,8 +51,8 @@ LL | | /// let x = 12;
51
51
LL | | /// ```
52
52
| |_______^
53
53
|
54
-
= help: there is an attribute with a similar name: `test_harness`
55
-
= help: the code block will either not be tested if not marked as a rust one or the code will be wrapped inside a main function
54
+
= help: use `test_harness` to run functions marked `#[test]` instead of a potentially-implicit `main` function
55
+
= help: this code block may be skipped during testing, because unknown attributes are treated as markers for code samples written in other programming languages, unless it is also explicitly marked as `rust`
0 commit comments