Generated `Inscribe` mark isn't very unique

[tob-joe]

Struct names clash in Rust easily and idiomatically, which might cause issues -- e.g. there are approximately a billion types called PublicKey.

I'm not sure the best way to get a unique name for a given struct -- I don't know an easy way to get a "fully-qualified" version of struct names that would include crate/namespace info, but that would be ideal.

This seems like something that other people would have run into before, and Rust's macro/type magic should be able to handle it. https://docs.rs/mononym/latest/mononym/ seems like it might be promising? But I'm not sure if it actually addresses what we need here.

[opal-escent]

This is a really good point. I've been looking to see if there's a good way to get a "fully-qualified" name, but everything I'm seeing says that macros are run before name resolution, so there's no real way to get that at compile-time.

I think documentation might be the best solution here. I'll update the README to reflect this limitation and encourage users to override it. I think this will be a lot easier if we update the structure to incorporate the constant string approach discussed elsewhere.

[cmlsharp]

Why not make the default implementation of get_mark

    fn get_mark(&self) -> &'static str {
        std::any::type_name::<Self>()
    }

type_name returns the fully qualified type as a 'static str. Is there a reason you need to know the actual fully qualified type in the proc macro?

Edit: Ah the documentation warns that this is not suitable for a unique identifier (and somewhat worryingly it may not be the same across different versions of the compiler).

std::any::TypeId is globally unique, but it is almost entirely opaque, so there's likely not much you can do with it.