silentbyte / nameof Goto Github PK

Given this code:

static mut TEST: u8 = 0;

fn main() {
    println!("{}", ::nameof::name_of!(TEST));
}

the compiler fails with this error:

error[E0133]: use of mutable static is unsafe and requires unsafe function or block
 --> src/main.rs:4:20
  |
4 |     println!("{}", ::nameof::name_of!(TEST));
  |                    ^^^^^^^^^^^^^^^^^^^^^^^^ use of mutable static
  |
  = note: mutable statics can be mutated by multiple threads: aliasing violations or data races will cause undefined behavior
  = note: this error originates in the macro `::nameof::name_of` (in Nightly builds, run with -Z macro-backtrace for more info)

For more information about this error, try `rustc --explain E0133`.
error: could not compile `bug-repro-rust-nameof-unsafe` due to previous error

It's currently not possible to use name_of_type!(Self) to get the actual type name. If there is a way to support this, that would be great, but until then, it would be nice to automatically suppress clippy::use_self warning in the macro.

return crate::test &str

The release should have been a feature release, because a crate might depend on the new functionality introduced with 1.0.2 (being able to use name_of!(type ...) without importing name_of_type!).

This might be an issue in the following situation:

Given that crate A depends on crate B and the following versions:

When crate B uses the new feature from 1.0.2, crate A fails to build.

I recommend releasing two new versions:

• 1.0.3 (Identical to 1.0.1)
• 1.1.0 (Identical to 1.0.2)

Also 1.0.2 should be yanked from crates.io.

Co-written-by: @bash

Originally posted by @jeremystucki in #1 (comment)

In new nightly name_of! macro generates "unused closure that must be used" warning.

I think, let _ = should be added to suppress the warning.

Hi,
I'm trying to implement Debug or Format for enums (yes, I know about the derive) and
don't want to hardcode enum tag names as strings.
Potentially, enum tags can change names in future and I want to be sure that print-ed values will follow names.
Was thinking about using nameof for this. For instance:

    enum Color {
        Red(i32),
        Green(i32),
        Blue(i32),
    }
   
    name_of!(enum Color::Green(42));
   // or
   tag_of!(Color::Green(42));