@@ -80,41 +80,11 @@ approachable and practical; it may make sense to direct users to an RFC or some
8080other issue for the full details. The issue also serves as a place where users
8181can comment with questions or other concerns.
8282
83- A template for these breaking-change tracking issues can be found below. An
84- example of how such an issue should look can be [ found
83+ A template for these breaking-change tracking issues can be found
84+ [ here ] [ template ] . An example of how such an issue should look can be [ found
8585here] [ breaking-change-issue ] .
8686
87- The issue should be tagged with (at least) ` B-unstable ` and ` T-compiler ` .
88-
89- ### Tracking issue template
90-
91- This is a template to use for tracking issues:
92-
93- ```
94- This is the **summary issue** for the `YOUR_LINT_NAME_HERE`
95- future-compatibility warning and other related errors. The goal of
96- this page is describe why this change was made and how you can fix
97- code that is affected by it. It also provides a place to ask questions
98- or register a complaint if you feel the change should not be made. For
99- more information on the policy around future-compatibility warnings,
100- see our [breaking change policy guidelines][guidelines].
101-
102- [guidelines]: LINK_TO_THIS_RFC
103-
104- #### What is the warning for?
105-
106- *Describe the conditions that trigger the warning and how they can be
107- fixed. Also explain why the change was made.**
108-
109- #### When will this warning become a hard error?
110-
111- At the beginning of each 6-week release cycle, the Rust compiler team
112- will review the set of outstanding future compatibility warnings and
113- nominate some of them for **Final Comment Period**. Toward the end of
114- the cycle, we will review any comments and make a final determination
115- whether to convert the warning into a hard error or remove it
116- entirely.
117- ```
87+ [ template ] : https://github.com/rust-lang/rust/issues/new?template=tracking_issue_future.md
11888
11989### Issuing future compatibility warnings
12090
0 commit comments