rust/compiler/rustc_log, branch masterhttps://github.com/rust-lang/rust
http://git.dreamy.place/mirrors/rust/atom?h=master2025-09-08T16:23:37+00:00Update tracing, again2025-09-08T16:23:37+00:00Daniel Paoliellodanpao@microsoft.com2025-09-04T00:12:03+00:00urn:sha1:266f8c9c0073745044a8eaeef5803b90090f5ad5rustc_log: remove direct dep on tracing_core2025-09-04T10:25:11+00:00klensyklensy@users.noreply.github.com2024-07-04T11:47:37+00:00urn:sha1:267d3c85088ebea128ef4b88435ceda937f306cd
required features reexported from tracing
unpin tracing_core2025-09-04T10:24:42+00:00klensyklensy@users.noreply.github.com2024-07-04T11:43:27+00:00urn:sha1:17b27d8e6c7ecce909d3b0bd072378c7a0854d78Revert introduction of `[workspace.dependencies]`.2025-09-02T09:12:54+00:00Nicholas Nethercoten.nethercote@gmail.com2025-09-02T09:09:13+00:00urn:sha1:301655eafe56a4b5064adebd412becf94b59221c
This was done in #145740 and #145947. It is causing problems for people
using r-a on anything that uses the rustc-dev rustup package, e.g. Miri,
clippy.
This repository has lots of submodules and subtrees and various
different projects are carved out of pieces of it. It seems like
`[workspace.dependencies]` will just be more trouble than it's worth.
Add `tracing` to `[workspace.dependencies]`.2025-08-27T04:21:19+00:00Nicholas Nethercoten.nethercote@gmail.com2025-08-22T00:39:58+00:00urn:sha1:c50d2cc8078280a0dfdd562c7688e81b664e5880Add documentation for init_logger_with_additional_layer2025-06-12T10:11:15+00:00Stypoxstypox@pm.me2025-06-12T10:09:55+00:00urn:sha1:781baafbe4501e079489f76fdd6fb439252f467dUse closure to allow passing custom tracing layers2025-06-11T08:42:50+00:00Stypoxstypox@pm.me2025-06-11T08:23:43+00:00urn:sha1:fc96ca8bbad7fb4c7546fb98807e826723fc6c1d
The previous method, where a layer would be passed directly,
required to pass a "no-op" layer when no custom layer was needed.
This should have in theory worked, however having a no-op layer
seems to change the way the tracing lib applies filters internally,
leading to some debug!() being printed despite them being out of
the minimum level for the filters. Note however that this behavior
was very inconsistent, and e.g. some debug!() would get printed
and some others wouldn't, for no apparent reason.
Allow initializing logger with additional tracing Layer2025-06-11T08:41:22+00:00Stypoxstypox@pm.me2025-05-12T14:27:09+00:00urn:sha1:0d74252537b6fd3ae6287486dbeec437cf021efaAllow linking rustc and rustdoc against the same single tracing crate2025-05-03T17:18:50+00:00David Tolnaydtolnay@gmail.com2025-05-03T16:57:20+00:00urn:sha1:00d3fdce7cb36a8c3fa090f797bdd093665cbe93
By consecutively initializing `tracing` and `rustc_log`, Rustdoc assumes
that these involve 2 different tracing crates.
I would like to be able to build rustdoc against the same tracing crate
that rustc_log is also built against. Previously this arrangement would
crash rustdoc:
thread 'main' panicked at rust/compiler/rustc_log/src/lib.rs:142:65:
called `Result::unwrap()` on an `Err` value: SetGlobalDefaultError("a global default trace dispatcher has already been set")
stack backtrace:
0: rust_begin_unwind
1: core::panicking::panic_fmt
2: core::result::unwrap_failed
3: rustc_log::init_logger
4: rustc_driver_impl::init_logger
5: rustdoc::main
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.
error: the compiler unexpectedly panicked. this is a bug.
note: we would appreciate a bug report: https://github.com/rust-lang/rust/issues/new?labels=C-bug%2C+I-ICE%2C+T-rustdoc&template=ice.md
note: please make sure that you have updated to the latest nightly
query stack during panic:
end of query stack
Use `-Wunused_crate_dependencies` for compiler crates.2025-03-19T21:59:43+00:00Nicholas Nethercoten.nethercote@gmail.com2025-03-03T07:59:30+00:00urn:sha1:8121958fda43759fa94e3f74f7cdbb595ddcc0e5
It's very useful. There are some false positives involving integration
tests in `rustc_pattern_analysis` and `rustc_serialize`. There is also a
false positive involving `rustc_driver_impl`'s
`rustc_randomized_layouts` feature. And I removed a `rustc_span` mention
in a doc comment in `rustc_log` because it wasn't integral to the
comment but caused a dev-dependency.