diff options
| author | Yuki Okushi <jtitor@2k36.org> | 2022-06-21 20:08:09 +0900 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2022-06-21 20:08:09 +0900 |
| commit | 9c800ec4e97ec92c5b9b2ae2bd3f2aeeb4146df6 (patch) | |
| tree | 139c60ac7c3fa139db9cb9769a003038b0815035 /compiler/rustc_llvm/llvm-wrapper/RustWrapper.cpp | |
| parent | b20aff2b334f9e3372a8220e6e36b3907a01e48e (diff) | |
| parent | 976336dab036f8eb7a54700068a32210e0dbc916 (diff) | |
| download | rust-9c800ec4e97ec92c5b9b2ae2bd3f2aeeb4146df6.tar.gz rust-9c800ec4e97ec92c5b9b2ae2bd3f2aeeb4146df6.zip | |
Rollup merge of #97805 - coolreader18:trace-suggestions, r=oli-obk
Add proper tracing spans to rustc_trait_selection::traits::error_reporting While I was trying to figure out #97704 I did some of this to make the logs more legible, so I figured I'd do the whole module and open a PR with it. afaict this is an ongoing process in the compiler from the log->tracing transition? but lmk if there was a reason for the more verbose forms of logging as they are. Also, for some of the functions with only one log in them, I put the function name as a message for that log instead of `#[instrument]`-ing the whole function with a span? but maybe the latter would actually be preferable, I'm not actually sure.
Diffstat (limited to 'compiler/rustc_llvm/llvm-wrapper/RustWrapper.cpp')
0 files changed, 0 insertions, 0 deletions