Yet here we have an example of bad developer ergonomics that so frustrates one developer that they are willing to use whatever bonkers syntax they can get the p

Yet here we have an example of bad developer ergonomics that so frustrates one developer that they are willing to use whatever bonkers syntax they can get the parser to choke down, and build an AST transformer for Go, to try to get something remotely approximating sane for a single common case. Which is saying nothing of Go libraries heavily relying on comment-based programming (err, sorry, we call them "struct tags") to generate boilerplate. The language is successful, but "expense of developer ergonomics" is an understatement.