From dae548698a3cc92286accf3d4d4926e572c4d3a1 Mon Sep 17 00:00:00 2001 From: Ed Page Date: Tue, 18 Nov 2025 13:52:15 -0600 Subject: [PATCH] docs(guide): When suggesting alt dev profile, link to related issue Having sections in the build performance chapter link out to their issues is helpful for: - giving hope that things will improve - providing a place for people to subscribe to for updates - raise visibility for ensuring we get appropriaet feedback (e.g. on degrading the debugger experience) Noticed this was missing while writing up about this new chapter on the blog post. --- src/doc/src/guide/build-performance.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/src/doc/src/guide/build-performance.md b/src/doc/src/guide/build-performance.md index 8d7ac5481b2..9afd31031a3 100644 --- a/src/doc/src/guide/build-performance.md +++ b/src/doc/src/guide/build-performance.md @@ -45,6 +45,8 @@ This will: - Avoid generating any debug information for dependencies - Provide an opt-in for when debugging via [`--profile debugging`](../reference/profiles.md#custom-profiles) +> **Note:** re-evaluating the `dev` profile is being tracked in [#15931](https://github.com/rust-lang/cargo/issues/15931). + Trade-offs: - ✅ Faster code generation (`cargo build`) - ✅ Faster link times