docs(refs): Add unsafe
to extern
while using build scripts in Cargo Book
#15294
+5
−5
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.
What does this PR try to resolve?
Since
rust 1.85.0
, It is no longer sufficient to use theunsafe
keyword only at the call site. It must also be applied to theextern
statement, hence, Cargo Book must be updatedand also update some more related content
How should we test and review this PR?
Run
mdbook build
. Theunsafe extern
should be seen atcargo/reference/build-script-examples.html#linking-to-system-libraries
,cargo/reference/build-script-examples.html#building-a-native-library
,cargo/reference/semver.html#repr-c-shuffle
,cargo/reference/semver.html#repr-c-remove
andcargo/reference/semver.html#repr-transparent-remove
Additional information