30
Go proposal: Leave “if err != nil” alone?
source link: https://www.tuicool.com/articles/U7ZNZjU
Go to the source link to view the article. You can view the picture content, updated content and better typesetting reading experience. If the link is broken, please click the button below to view the snapshot at that time.
The Go2 proposal #32437
adds new syntax to the language to make the if err != nil { return ... }
boilerplate less cumbersome.
There are various alternative proposals: #32804 and #32811 as the original one is not universally loved.
To throw another alternative in the mix: Why not keep it as is ?
I've come to like the explicit nature of the if err != nil
construct and as such I don't understand why we need new syntax for this. Is it really that bad?
Recommend
About Joyk
Aggregate valuable and interesting links.
Joyk means Joy of geeK