diff options
| author | Matthias Krüger <matthias.krueger@famsik.de> | 2024-03-15 10:14:54 +0100 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2024-03-15 10:14:54 +0100 |
| commit | f4afbe138927d3d3ac31e898d6d388179514156e (patch) | |
| tree | bd0aeebf76fdb6bb109880da166f9aa004d29173 /compiler/rustc_codegen_llvm/src | |
| parent | e66c7e479c14ad9fcb48e96ce8b7cdb161be0d26 (diff) | |
| parent | 48f2f0d725e6d484af24e4666992cc66b6a31ebd (diff) | |
| download | rust-f4afbe138927d3d3ac31e898d6d388179514156e.tar.gz rust-f4afbe138927d3d3ac31e898d6d388179514156e.zip | |
Rollup merge of #122471 - RalfJung:const-eval-span, r=oli-obk
preserve span when evaluating mir::ConstOperand This lets us show to the user where they were using the faulty const (which can be quite relevant when generics are involved). I wonder if we should change "erroneous constant encountered" to something like "the above error was encountered while evaluating this constant" or so, to make this more similar to what the collector emits when showing a "backtrace" of where things get monomorphized? It seems a bit strange to rely on the order of emitted diagnostics for that but it seems the collector already [does that](https://github.com/rust-lang/rust/blob/da8a8c9223722e17cc0173ce9490076b4a6d263d/compiler/rustc_monomorphize/src/collector.rs#L472-L475).
Diffstat (limited to 'compiler/rustc_codegen_llvm/src')
0 files changed, 0 insertions, 0 deletions