diff options
| author | Jubilee <workingjubilee@gmail.com> | 2024-09-15 23:51:24 -0700 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2024-09-15 23:51:24 -0700 |
| commit | 0151cbe6e8ca1027f5482c98a1b93d70fbd9a50b (patch) | |
| tree | 10bd497472d9bce7206b3da687fc7bddf054db4a /compiler/rustc_codegen_llvm/src/intrinsic.rs | |
| parent | 39b7669347b02f25a36da610822fb3c1e03bac6c (diff) | |
| parent | 56fb89acee048c80b595f42cdcb749ed39a43e10 (diff) | |
| download | rust-0151cbe6e8ca1027f5482c98a1b93d70fbd9a50b.tar.gz rust-0151cbe6e8ca1027f5482c98a1b93d70fbd9a50b.zip | |
Rollup merge of #127879 - kornelski:bad-pointer-printf, r=workingjubilee
Document futility of printing temporary pointers
In the user forum I've seen a few people trying to understand how borrowing and moves are implemented by peppering their code with printing of `{:p}` of references to variables and expressions. This is a bad idea. It gives misleading and confusing results, because of autoderef magic, printing pointers of temporaries on the stack, and/or causes LLVM to optimize code differently when values had their address exposed.
Diffstat (limited to 'compiler/rustc_codegen_llvm/src/intrinsic.rs')
0 files changed, 0 insertions, 0 deletions