When building file paths for logging, the output is full of absolute paths, making the output illegible and also leaking information about the system where the final binary was compiled on (project root, cargo registry root, username of whoever compiled, etc).
I'd like to request a method (probably two different macros) to fetch the crate name and the file location relative to the crate root directory that could be used by the log crate to build much better log messages. Just like file!, this needs to point to the location of the invocation of the first macro, if nested.
When looking through logs, and I'm outputting file paths and line numbers these are actually what I'm looking for: which crate it is, and which file it is within that crate.