<#17685 go: what to name a compiler flags field?> ...
# github-notifications
q
#17685 go: what to name a compiler flags field? New discussion created by tdyas What should we name the field on Go target types for adding extra compiler flags to compilation of Go files? In #17683, I've called the field
compiler_flags
but that seems too verbose and could be better. Some ideas: •
compile_flags
build_flags
compile_opts
build_opts
Bazel calls its equivalent field
gc_goopts
where
gc
means "Go compiler" and
goopts
is Go options. This naming convention will also be used for assembler and linker flags as well. Maybe
asm_flags
and
link_flags
? Or
assembler_flags
or
linker_flags
? pantsbuild/pants