diff options
| author | bors <bors@rust-lang.org> | 2022-03-02 17:05:06 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2022-03-02 17:05:06 +0000 |
| commit | 14f3d059398378a3878fc11242271017af122e80 (patch) | |
| tree | 6e1bf0e657dc13678b39f9b9610120850b19861f /src/test/codegen/src-hash-algorithm | |
| parent | 1a25d190e7a33e2955a7cb8c18b80f857f4e048f (diff) | |
| parent | fd9dd04972252bc709fc0e477c7b8f6796d3f1e1 (diff) | |
| download | rust-14f3d059398378a3878fc11242271017af122e80.tar.gz rust-14f3d059398378a3878fc11242271017af122e80.zip | |
Auto merge of #8432 - dtolnay-contrib:transmuteundefinedrepr2, r=Manishearth
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
Diffstat (limited to 'src/test/codegen/src-hash-algorithm')
0 files changed, 0 insertions, 0 deletions