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
Auto merge of rust-lang#141011 - matthiaskrgr:rollup-4uwllo2, r=matthiaskrgr
Rollup of 7 pull requests
Successful merges:
- rust-lang#140827 (Do not ICE when reassigning in GatherLocalsVisitor on the bad path)
- rust-lang#140904 (Add an issue template for future-incompatible lints)
- rust-lang#140953 (Fix a compiletest blessing message)
- rust-lang#140973 (Update rustix to 1.0.7 for bootstrap)
- rust-lang#140976 (Add `Ipv4Addr` and `Ipv6Addr` diagnostic items)
- rust-lang#140988 (MaybeUninit::write: fix doc)
- rust-lang#140989 (Suggest replace f with f: Box<f> when expr field is short hand)
r? `@ghost`
`@rustbot` modify labels: rollup
Thank you for creating a future-incompatible tracking issue! 📜 These issues
9
+
are for lints that implement a future-incompatible warning.
10
+
11
+
Remember to add team labels to the tracking issue.
12
+
For something that affects the language, this would be `T-lang`, and for libs
13
+
it would be `T-libs-api`.
14
+
Also check for any `A-` labels to add.
15
+
-->
16
+
17
+
This is the **tracking issue** for the `YOUR_LINT_NAME_HERE` future-compatibility warning and other related errors. The goal of this page is describe why this change was made and how you can fix code that is affected by it. It also provides a place to ask questions or register a complaint if you feel the change should not be made. For more information on the policy around future-compatibility warnings, see our [breaking change policy guidelines][guidelines].
*Describe the conditions that trigger the warning.*
24
+
25
+
### Why was this change made?
26
+
27
+
*Explain why this change was made. If there is additional context, like an MCP, link it here.*
28
+
29
+
### Example
30
+
31
+
```rust
32
+
// Include an example here.
33
+
```
34
+
35
+
### Recommendations
36
+
37
+
*Give some recommendations on how a user can avoid the lint.*
38
+
39
+
### When will this warning become a hard error?
40
+
41
+
*If known, describe the future plans. For example, how long you anticipate this being a warning, or if there are other factors that will influence the anticipated closure.*
42
+
43
+
### Steps
44
+
45
+
-[ ] Implement the lint
46
+
-[ ] Raise lint level to deny
47
+
-[ ] Make lint report in dependencies
48
+
-[ ] Switch to a hard error
49
+
50
+
### Implementation history
51
+
52
+
<!--
53
+
Include a list of all the PRs that were involved in implementing the lint.
= note: for more on the distinction between the stack and the heap, read https://doc.rust-lang.org/book/ch15-01-box.html, https://doc.rust-lang.org/rust-by-example/std/box.html, and https://doc.rust-lang.org/std/boxed/index.html
10
+
help: store this in the heap by calling `Box::new`
= note: for more on the distinction between the stack and the heap, read https://doc.rust-lang.org/book/ch15-01-box.html, https://doc.rust-lang.org/rust-by-example/std/box.html, and https://doc.rust-lang.org/std/boxed/index.html
24
+
help: store this in the heap by calling `Box::new`
0 commit comments