Skip to content

Commit 3c71917

Browse files
weihangloepage
andauthored
fix: clarify why persisting timing data matters
Co-authored-by: Ed Page <[email protected]>
1 parent 1bb7f21 commit 3c71917

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

src/2025h2/cargo-build-analysis.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -30,7 +30,7 @@ Cargo does not persist information about previous builds.
3030
While the [`--timings`] flag provides per-build data on how long each unit takes to compile,
3131
this information:
3232

33-
* Is tied to a single build session
33+
* You have to know you will care about a timings report and can't look it up afterwards
3434
* Exists primarily in HTML form, which is not suited for machine analysis
3535

3636
Additionally, Cargo does not track:

0 commit comments

Comments
 (0)