Re: [PATCH] rust: introduce sfile macro for easier code tracing

[Timur Tabi <ttabi@nvidia.com>]

On Thu, 2025-06-05 at 08:07 +0200, Greg KH wrote:
> > Maybe dbs!(), or just d!() ?
> 
> Wait, why are we trying to reimplement the existing pr_dbg() code in a
> non-standard-way?

pr_dbg() is not changing.  We're talking about the standard Rust macro dbg!()

	https://doc.rust-lang.org/std/macro.dbg.html

the "problem" with dbg! is that it uses file!(), which outputs the full relative path of the
source file, which can be quite lengthy.  IOW, I think dbg!() is often too noisy.

And we're not talking about changing dbg!() either.  In cases where a given Rust driver has
multiple source files of the same name but in different paths, you probably want dbg!() to use
file!().

But in situations where you don't have that file layout, maybe you would prefer the output of my
sfile!() macro.

I'll be honest, this thing has blown up more than I expected.  I got a lot of positive feedback
from my patch that has not only improved the code, but also taught me a lot about Rust itself. 
So even if this whole thing gets nack'd, I won't be too upset.  I'll just keep using sfile! for
my own purposes.

But I am excited about the *possibility* that we can make everyone happy with my code.