Hygienic synthetic targets #17504
Replies: 2 comments 1 reply
-
... uh, you're welcome? :) |
Beta Was this translation helpful? Give feedback.
-
This is sortof like what Alternatively, if synthetic targets had names which were impossible to collide with (because they exist in a namespace that targets defined in Finally: assuming that you can think of an API that amounts to "the caller creating a synthetic target at request time, without having to choose a name for it", then the macro that wants to consume it wouldn't have to choose or know a name. |
Beta Was this translation helpful? Give feedback.
-
Stu:
Originally posted by @stuhood 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?
Beta Was this translation helpful? Give feedback.
All reactions