v0.4.2
Adds a stronger uniqueness guarantee to new_unique_export_tokens_ident
by incorporating a compilation-unique tag.
This will resolve situations where crates using separate instances of macro_magic that happen to have #[export_tokens]
declarations that use the same name and happen to have the same COUNTER
value are glob imported into the same module/scope.
Though these scenarios are already exceedingly rare, after this change for this to happen again two separate macro_magic compilations would also have to have their COMPILATION_TAG: u32
value collide, which is as unlikely as two random u32
values colliding, in addition to all of the other collision requirements laid out above. So this shouldn't be an issue anymore for anyone. If it does happen, you can rest assured it will go away after a fresh compile unless the universe truly despises you.