Some nuances: • If a normal

go_package

depends on the generated code, it will get compiled as a precursor • We don't have

./pants check

run directly on third-party packages for Go. You have to compile by depending on it in a

go_package

. We didn't like the UX of

./pants check path/to/go.mod

resulting in compiling every single thing because most packages aren't consumed • reminder that you can use

./pants export-codegen

to check already that Protoc spits out files. Technically those files might not be compileable tho It would require some rework of FieldSets to get this working. But for now only trying to figure out what is optimal design

(as that’s how the JVM selects its inner nodes: https://github.com/pantsbuild/pants/blob/6a37a0e7371bad085d3c806f64adf15a85c387c9/src/python/pants/jvm/compile.py#L50-L76)

basically,

FieldSet.is_applicable(target, union_membership)

would check whether sources fields could be converted.