docs: add disadvantages section to accepting-strings idiom #447
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.
📄 Description
This PR adds content to the previously empty "Disadvantages" section of the
accepting-strings
idiom.The section outlines the potential trade-offs and caveats when working with
&CStr
in FFI contexts, including:These additions aim to give developers a clearer understanding of the limitations and risks, complementing the advantages already described.
🔍 Motivation
The "Disadvantages" section was previously marked as
None?
. This contribution completes that section with relevant, up-to-date notes based on current Rust FFI practices (as of Rust 1.77+).✅ Checklist
accepting-strings.md
)docs:
convention