#17504 Hygienic synthetic targets New discussion created by kaos Stu:

This problem (from #17365) seems loosely related to the idea of "hygienic macros": i.e., that a macro should be able to define anonymous variables which can't collide with or pollute the original namespace. But I don't know how to do that and still have consumers later depend-on/find them... maybe by having the request for the synthetic target use something other than its name/address?

Originally posted by @witty-crayon-22786 in #17365 (review) My idea being we could open up a discussion about synthetic target hygiene. I know @Eric-Arellano wanted the synthetic targets to live in their own namespace, or something like that. While the synthetic targets needs to exist also in the regular target namespace (to be able to being target for dependencies and extension by BUILD file targets), perhaps it would be useful to be able to reach also shadowed synthetic targets in some way? pantsbuild/pants