I agree. I like the filename based constraints, but having both is annoying and since the comment based constraints are more flexible I think they'd have to be the ones to stay. I frequently find myself looking for constraints by grepping for whatever it is I want, but if I have filename based constraints I have to do a find as well. Having one or another but not both would make my life easier in a small but meaningful way.
—Sam On Tue, Jun 30, 2020, at 18:56, roger peppe wrote: > One thing I'd really like to see is the eventual deprecation of filename- > based build constraints (e.g. file_linux.go). They make it hard for > users (not everyone knows the name of all architectures), hard for > tooling (tools need to maintain a list of current architectures) and > potentially compatibility-breaking (adding a new architecture can > change the meaning of existing files). Could we eventually mandate in- > file build constraints instead? -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/09cfada5-0e6d-4e0b-9d63-6e5963530a42%40www.fastmail.com.
