One aspect of go error handling that still really bothers me is how easy it is to accidentally drop an error on the floor. If you strap all the linters you can

One aspect of go error handling that still really bothers me is how easy it is to accidentally drop an error on the floor. If you strap all the linters you can find onto your build system, you can catch the most obvious cases. But I still frequently find mishandled errors that sneak past the linters in ways that can't be solved without restricting the way devs use the language. By making error handling something you have to deal with every time you call a function, you massively increase the number of opportunities you have for screwing it up. I would love something like rusts ? Operator for go. You could choose to not use it when you need special handling. But it would be rare and exciting and developers would use it with care.