about summary refs log tree commit diff
path: root/compiler/rustc_codegen_gcc/example/alloc_example.rs
diff options
context:
space:
mode:
authorTrevor Gross <t.gross35@gmail.com>2025-05-27 20:28:32 -0400
committerGitHub <noreply@github.com>2025-05-27 20:28:32 -0400
commite0278ed5afa50b889c7f6c5f844726cd8c18f55c (patch)
treeded667dc59ec7abf2ac85da9cb945d2694cd9108 /compiler/rustc_codegen_gcc/example/alloc_example.rs
parenta8c7a1e29bc2a9ded5db661a04c4f91adaaf745e (diff)
parent295a8d56f5a7d200599d587fb52bf217b9aee363 (diff)
downloadrust-e0278ed5afa50b889c7f6c5f844726cd8c18f55c.tar.gz
rust-e0278ed5afa50b889c7f6c5f844726cd8c18f55c.zip
Rollup merge of #141551 - compiler-errors:hir-lints, r=BoxyUwU
Make two transmute-related MIR lints into HIR lint

Make `PTR_TO_INTEGER_TRANSMUTE_IN_CONSTS` (rust-lang/rust#130540) and `UNNECESSARY_TRANSMUTES` (rust-lang/rust#136083) into "normal" HIR-based lints.

Funny enough this came up in the review of the latter (https://github.com/rust-lang/rust/pull/136083#issuecomment-2614301413), but I guess it just was overlooked.

But anywyas, there's no reason for these to be MIR lints; in fact, it makes the suggestions for them a bit more complicated than necessary.

Note that there's probably a few more simplifications and improvements to be done here. Follow-ups can be done in a separate PR, especially if they're about the messaging and suggestions themselves, which I didn't write.
Diffstat (limited to 'compiler/rustc_codegen_gcc/example/alloc_example.rs')
0 files changed, 0 insertions, 0 deletions