Fix transmute_undefined_repr with single field #[repr(C)] structs
#8425
Conversation
This file contains 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
|
r? @giraffate (rust-highfive has picked a reviewer for you, use r? to override) |
rust-highfive
added
the
S-waiting-on-review
giraffate
approved these changes
Feb 14, 2022
|
@bors r+ It looks good, thanks! |
|
📌 Commit 662df33 has been approved by |
bors
added a commit
that referenced
this pull request
Feb 14, 2022
Fix `transmute_undefined_repr` with single field `#[repr(C)]` structs Fixes: #8417 The description has also been made more precise. changelog: Fix `transmute_undefined_repr` with single field `#[repr(C)]` structs changelog: Move `transmute_undefined_repr` back to `correctness`
|
💥 Test timed out |
|
@bors retry |
|
☀️ Test successful - checks-action_dev_test, checks-action_remark_test, checks-action_test |
bors
added a commit
that referenced
this pull request
Mar 2, 2022
…shearth Transmute_undefined_repr to nursery again This PR reinstates #8418, which was reverted in #8425 (incorrectly I think). I don't want to start a revert war over this but I feel very strongly that this lint is not in a state that would be a net benefit to users of clippy. In its current form, making this an enabled-by-default `correctness` lint with authoritative-sounding proclamations of undefined behavior does more harm than the benefit of the true positive cases. I can file a bunch more examples of false positives but I don't want to give the author of this lint the impression that it is ready to graduate from `nursery` as soon as I've exhausted the amount of time I am willing to spend revising this lint. Instead I would recommend that the author of the lint try running it on some reputable codebases containing transmutes. Everywhere that the lint triggers please consider critically whether it should be triggering. For cases that you think are true positives, please raise a few of them with the crate authors (in a PR or issue) to better understand their perspective if they think the transmute is correct. --- *Please write a short comment explaining your change (or "none" for internal only changes)* changelog: Re-remove [`transmute_undefined_repr`] from default set of enabled lints
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Fixes: #8417
The description has also been made more precise.
changelog: Fix
transmute_undefined_reprwith single field#[repr(C)]structschangelog: Move
transmute_undefined_reprback tocorrectness