docs(cargo): clarify immediate-abort selection in config.toml comment#248
Merged
Conversation
chcmedeiros
force-pushed
the
fix/cargo-config-comment
branch
from
04ab112 to
1ada82b
Compare
chcmedeiros
force-pushed
the
fix/cargo-config-comment
branch
from
1ada82b to
28c2bb1
Compare
emmanuelm41
approved these changes
Jun 23, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The comment in
app/rust/.cargo/config.tomlstill described the old-Cpanic=immediate-abortrustflag approach. Updated it to reflect how immediate-abort is actually selected now: viapanic = "immediate-abort"in[profile.release]ofCargo.toml(gated bycargo-features = ["panic-immediate-abort"]), withcorerebuilt through-Z build-std=coreon the device build command. Comment-only change.