Skip to content

Commit d5c6fb1

Browse files
committed
Link the appendix
1 parent 9ea5e0e commit d5c6fb1

File tree

1 file changed

+3
-1
lines changed

1 file changed

+3
-1
lines changed

docs/authoring.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -101,7 +101,7 @@ When assigning rules to new paragraphs, or when modifying rule names, use the fo
101101

102102
#### Test rule annotations
103103

104-
Tests in <https://github.com/rust-lang/rust> can be linked to rules in the reference. The rule will include a link to the tests, and there is also an appendix which tracks how the rules are currently linked.
104+
Tests in <https://github.com/rust-lang/rust> can be linked to rules in the reference. The rule will include a link to the tests, and there is also an [appendix] which tracks how the rules are currently linked.
105105

106106
Tests in the `tests` directory can be annotated with the `//@ reference: x.y.z` header to link it to a rule. The header can be specified multiple times if a single file covers multiple rules.
107107

@@ -111,6 +111,8 @@ Prefixed rule names should not be used in tests. That is, do not use something l
111111

112112
We are not expecting 100% coverage at any time. Although it would be nice, it is unrealistic due to the sequence things are developed, and resources available.
113113

114+
[appendix]: https://doc.rust-lang.org/nightly/reference/test-summary.html
115+
114116
### Standard library links
115117

116118
You should link to the standard library without specifying a URL in a fashion similar to [rustdoc intra-doc links][intra]. Some examples:

0 commit comments

Comments
 (0)