Skip to content

Commit 4c77d94

Browse files
committed
s@build/@target/@.
Also, fixed some text that clearly dates from the now-irrelevant issues we used to have with diagnostics on path-dependencies.
1 parent 5d4d98c commit 4c77d94

File tree

1 file changed

+6
-5
lines changed

1 file changed

+6
-5
lines changed

text/0000-cargo-report-future-incompat.md

Lines changed: 6 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -351,7 +351,7 @@ The responsibilities of Cargo:
351351
of the whole build.
352352

353353
* Cargo is responsible for storing a record of any future-incompatibility
354-
for a crate somewhere in the `build/` directory, so that it can
354+
for a crate somewhere in the `target/` directory, so that it can
355355
emit the same report without having to rebuild the crate on subsequent
356356
rebuilds of the root crate.
357357

@@ -394,10 +394,11 @@ Rust, if known, where it will become a hard error.
394394

395395
Since `cargo` is expected to continue to emit the report even when the
396396
upstream dependencies are not rebuilt, Cargo will store the
397-
future-incompatibility status for each crate somewhere in the `build/`
398-
directory on the file-system. (This is analogous to how incremental
399-
compilation caches diagnostic output, so that future runs will still
400-
emit the same report even when we do not recompile the same input.)
397+
future-incompatibility status for each crate somewhere in the `target/`
398+
directory on the file-system.
399+
(This should be a trivial constraint today: Cargo on the nightly channel
400+
is already locally caching warnings emitted while building upstream
401+
path-dependencies.)
401402

402403

403404
## Policy issues

0 commit comments

Comments
 (0)