Ah, I think it does matter. We want a consistent design language. This is why renaming

protobuf_library

matters too imo A big insight I've had recently is a separation between targets describing 1) your own code, 2) third-party reqs, and 3) artifacts. We used to muddy that, like

provides=setup_py()

being defined on a

python_library

target, or

pex_binary()

having a

sources

field. Now, we have targets whose sole purpose is describing source files vs. targets for abstract metadata on how to build something For that first category, I'm thinking

lang_sources

and

lang_tests

should scale well