David Barsky

I've confirmed that this is still an issue on rustc 1.77.0-nightly (a2d9d73e6 2024-01-10).

It's the CI warning that are holding it back, which is pretty annoying.

@leptonyu `tracing` exposes most of that data as references, so you'll need to `fmt` that data into a structure that _your_ code relies on. Depending on where `do_something` might be,...

@hawkw Finally! I made a new issue: https://github.com/tokio-rs/tracing/issues/905

I think I like the current design of the site more, but I think mdbook's ease of contribution outweighs that, IMO. I'm personally onboard with this!

> This feels like a very odd config to me I have to say 😅 Does VSCode hide elements in the status bar if the messages are too long? It...

> So I am still not on board with the idea of a config for this honestly speaking, not sure what to do here. > > > > Though now...

> > Overall implementation wise it looks good to me, al though I am still a bit on the fence wrt to having flycheck be in here. I am personally...

(Copying from https://github.com/rust-lang/rust-analyzer/issues/17363) I'm able to reproduce this: ```rust #[tracing::instrument] fn test() { let string = String::from("hello").replace("hello", "goodbye"); let string = String::from("goodbye").replace("goodbye", "goodbye"); } ``` Cargo.toml: ``` [package] name =...

Fair enough. I assume that the proc macro isn't helping, but I can make separate issues for them?