Added a unsafe_ffi_drop_implementations
lint.
#22078
Closed
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.
This detects cases where a struct or enum are annotated with
#[repr(C)]
,and do not have
#[unsafe_no_drop_flag]
, whereby it warns the user thatthe type may not have the expected size or layout.
The lint was set to "Warn" by default as I wasn't sure if "Deny" would be too strong.
A tangential change was to remove
#[repr(C)]
fromCleanup
insrc/libstd/sys/windows/backtrace.rs
. I believe this to be justified in thatCleanup
is only ever used exactly once as an RAII handle, and is never passed to any FFI function.Two tests including to ensure the lint triggers when
#[unsafe_no_drop_flag]
is missing, and does not trigger if it is present.Addresses #18380.