Generated #[instrument] code is not qualified to the tracing crate

[heaths]

Bug Report

Version

• tracing 0.1.40

Platform

Darwin Mac.localdomain 24.0.0 Darwin Kernel Version 24.0.0: Tue Sep 24 23:38:45 PDT 2024; root:xnu-11215.1.12~1/RELEASE_ARM64_T8122 arm64

Crates

tracing

Description

I created a tracing module in my crate to add a bunch of helpers for my use of the tracing crate. Probably not the best idea, but technical should work and naming is hard. I changed imports to use ::tracing::{instrument, Level} but then I was getting compiler errors like:

failed to resolve: could not find `span` in `tracing`
could not find `span` in `tracing`

failed to resolve: could not find `event` in `tracing`
could not find `event` in `tracing`

failed to resolve: could not find `Instrument` in `tracing`
could not find `Instrument` in `tracing`

lib.rs(9, 1): consider importing one of these traits: `use crate::instrument::Instrument;
`, `use ::tracing::Instrument;
`

If I rename my crate to something else - leaving the tracing crate import as either ::tracing or tracing, the generated code compiles fine. Perhaps the generated code should be emitting ::tracing as the prefix to avoid conflicts?

[Rustin170506]

Could you please provide a minimal reproducible Cargo project? That would help others reproduce the issue.

[heaths]

See https://play.rust-lang.org/?version=stable&mode=debug&edition=2021&gist=522a25ace0953c0a4568a7e2e8ca4d24

[heaths]

I opened 2 PRs: 1 each against master (v0.2.x?) and v0.1.x. We'd love to get at least a v0.1.28 of tracing-attributes. I can update this PR or submit another one if I should update any crates with a dependency on tracing-attributes e.g., tracing itself.