GCA: `tracing` crate is unusable
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 119k
- Forks
- 16.1k
- PR merge metrics
- PR metrics pending
Description
Code
I tried this code:
tracing::debug!(
%id,
adapter_info = ?adapter_info,
"Compatible adapter found"
);
This is something that works on stable and worked on nightly before. Now I added this to the crate (I used generic_const_exprs before):
#![feature(generic_const_args, generic_const_items, min_generic_const_args)]
I expected to see this happen: Code compiles
Instead, this happened:
error[E0107]: missing generics for struct `tracing::__macro_support::FieldName`
--> crates/farmer/ab-proof-of-space-gpu/src/host.rs:123:25
|
123 | / debug!(
124 | | %id,
125 | | adapter_info = ?adapter_info,
126 | | "Compatible adapter found"
127 | | );
| |_________________________^ expected 1 generic argument
|
note: struct defined here, with 1 generic parameter: `N`
--> /home/nazar-pc/.cargo/registry/src/index.crates.io-1949cf8c6b5b557f/tracing-0.1.44/src/lib.rs:1074:16
|
1074 | pub struct FieldName<const N: usize>([u8; N]);
| ^^^^^^^^^ --------------
= note: this error originates in the macro `$crate::__tracing_stringify` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info)
help: add missing generic argument
--> /home/nazar-pc/.cargo/registry/src/index.crates.io-1949cf8c6b5b557f/tracing-0.1.44/src/macros.rs:3250:47
|
3250 | $crate::__macro_support::FieldName<N>::len($crate::__macro_support::stringify!($($k).+))
| +++
Version it worked on
Any stable version, nightly at least until nightly-2026-05-03 (without GCA)
Version with regression
rustc --version --verbose:
rustc 1.98.0-nightly (cced03bfd 2026-05-28)
binary: rustc
commit-hash: cced03bfd61a304243a34504618ecec86c17063f
commit-date: 2026-05-28
host: x86_64-unknown-linux-gnu
release: 1.98.0-nightly
LLVM version: 22.1.6
This is the version I'm using right now that has this issue, I didn't use GCA before so not sure when it regressed exactly.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the failure with the tracing::debug! snippet from crates/farmer/ab-proof-of-space-gpu/src/host.rs and the reported nightly compiler. Inspect tracing-0.1.44/src/macros.rs around the __tracing_stringify expansion and tracing-0.1.44/src/lib.rs where FieldName is defined; done means the example compiles again with generic const arguments enabled.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- compilers
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100