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`
0 commit comments