The only other symbol in consideration is using

@

for disambiguating when there are multiple owning targets for a file. For example,

demo/app.txt@:tgt1

vs.

demo/app.txt@:tgt2

. Right now, we avoid that ambiguity ever being an issue, as follows: - file arguments -> don’t use generated subtargets and use all the original owning targets - dep infeerence -> no-op - explicit BUILD files -> error I personally advocate sticking with that and not using

@

. It depends how much we care about making it ergonomic to have multiple owners over the same target.