Skip to content

Commit 82a8fb4

Browse files
committed
Auto merge of #10856 - ehuss:future-incompat-docs, r=epage
Small tweaks to the future-incompat docs. This contains a few changes to the future-incompat docs to try to make it a little clearer how it works, and some formatting and wording changes.
2 parents a0439d8 + 32cbfde commit 82a8fb4

File tree

1 file changed

+19
-6
lines changed

1 file changed

+19
-6
lines changed
Lines changed: 19 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1,24 +1,37 @@
11
### Future incompat report
22

3-
Cargo checks for future-incompatible warnings in all dependencies. These are warnings for
3+
Cargo checks for future-incompatible warnings in all dependencies. These are warnings for
44
changes that may become hard errors in the future, causing the dependency to
55
stop building in a future version of rustc. If any warnings are found, a small
66
notice is displayed indicating that the warnings were found, and provides
77
instructions on how to display a full report.
88

9+
For example, you may see something like this at the end of a build:
10+
11+
```text
12+
warning: the following packages contain code that will be rejected by a future
13+
version of Rust: rental v0.5.5
14+
note: to see what the problems were, use the option `--future-incompat-report`,
15+
or run `cargo report future-incompatibilities --id 1`
16+
```
17+
918
A full report can be displayed with the `cargo report future-incompatibilities
1019
--id ID` command, or by running the build again with
1120
the `--future-incompat-report` flag. The developer should then update their
1221
dependencies to a version where the issue is fixed, or work with the
1322
developers of the dependencies to help resolve the issue.
1423

15-
This feature can be configured through a `[future-incompat-report]`
16-
section in `.cargo/config`. Currently, the supported options are:
24+
## Configuration
1725

18-
```
26+
This feature can be configured through a [`[future-incompat-report]`][config]
27+
section in `.cargo/config.toml`. Currently, the supported options are:
28+
29+
```toml
1930
[future-incompat-report]
20-
frequency = FREQUENCY
31+
frequency = "always"
2132
```
2233

23-
The supported values for `FREQUENCY` are `always` and `never`, which control
34+
The supported values for the frequency are `"always"` and `"never"`, which control
2435
whether or not a message is printed out at the end of `cargo build` / `cargo check`.
36+
37+
[config]: config.md#future-incompat-report

0 commit comments

Comments
 (0)