Hmm, I don't know that putting this in pub is necessarily the right way to go, because that seems like it might end up stuffing lots in there, and makes the vis macro matcher rather more complicated. I'm not sure that pub(impl in super, crate) is something I'd want to see there -- especially if it started extending to other things in pub too, like the scopes from which fields are allowed to be mutated, say.
I think I prefer the separate construct, even if that other construct also takes a path.