I suppose that it depends upon what you mean by the word, “safe.”   It might work ... yes, it might ... but any change to the module would also affect what it meant, because it does not say what it means.   Instead, it is “clever.”   From a project management point of view, and/or from the point of view of a fellow team-member who might get really tired of being “bit,” no, it is not safe.

The intent of this construct was clear:   to allow you to list exactly which of the possibly very-many subroutines in the package, you actually intend to use.   It is specifically envisioned to be both descriptive and limiting, and should be used in that fashion.