Ability to use `linkme` in proc macros without requiring explicit dependency

[nazar-pc]

I have a procedural macro that outputs code with linkme, the problem is that it requires users of the macro to know about this and add linkme to explicit dependencies.

I'm wondering if it would be possible to add support for custom linkme path (rather than ::linkme) so I can customize it to point to re-exports.

Something like this:

#[distributed_slice(BENCHMARKS, linkme = "::other_crate::__private::linkme")]

This would be a big UX improvement for users of my crate.

[nazar-pc]

I can create a PR if this is a welcome change

[0xIO32]

Sounds promising to me

[jstarks]

This is already possible:

#[my_crate::linkme::distributed_slice(BENCHMARKS)]
#[linkme(crate = my_crate::linkme)]
static FOO: ...

[0xIO32]

I suppose this issue can be closed then?

[nazar-pc]

This is already possible:

#[my_crate::linkme::distributed_slice(BENCHMARKS)]
#[linkme(crate = my_crate::linkme)]
static FOO: ...

Is this documented anywhere? I double checked and I can't find it.

P.S. Already switched to inventory, which at least compiles under Miri (but doesn't run yet).