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
Copy file name to clipboardExpand all lines: STYLE.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -41,11 +41,11 @@ See https://highlightjs.org/ for a list of supported languages.
41
41
42
42
Rust examples are tested via rustdoc, and should include the appropriate annotations when tests are expected to fail:
43
43
44
-
*`edition2015` or `edition2018`— If it is edition-specific (see `book.toml` for the default).
45
-
*`no_run`— The example should compile successfully, but should not be executed.
46
-
*`should_panic`— The example should compile and run, but produce a panic.
47
-
*`compile_fail`— The example is expected to fail to compile.
48
-
*`ignore`— The example shouldn't be built or tested.
44
+
*`edition2015` or `edition2018`--- If it is edition-specific (see `book.toml` for the default).
45
+
*`no_run`--- The example should compile successfully, but should not be executed.
46
+
*`should_panic`--- The example should compile and run, but produce a panic.
47
+
*`compile_fail`--- The example is expected to fail to compile.
48
+
*`ignore`--- The example shouldn't be built or tested.
49
49
This should be avoided if possible.
50
50
Usually this is only necessary when the testing framework does not support it (such as external crates or modules, or a proc-macro), or it contains pseudo-code which is not valid Rust.
51
51
An HTML comment such as `<!-- ignore: requires extern crate -->` should be placed before the example to explain why it is ignored.
0 commit comments