this post was submitted on 24 Nov 2023
7 points (100.0% liked)

Go programming language discussion

1382 readers
1 users here now

founded 5 years ago
MODERATORS
whou@lemmy.ml
gregf@lemmy.ml
rek2@lemmy.ml
7
Should I use naked return? If not, why? If yes, when? (self.golang)
submitted 11 months ago by khoi to c/golang@lemmy.ml
3 comments fedilink hide all child comments
top 3 comments
sorted by: hot top controversial new old
[–] squirmy_wormy@lemmy.world 6 points 11 months ago (1 children)

This says when it's ok to use them and why it should be limited

https://go.dev/tour/basics/7

Personally, I don't like them. Makes things awkward to read imo

[–] ck_@discuss.tchncs.de 4 points 11 months ago

Yeah, I tend to agree, naked returns are hard to read and they don't really add much in terms of value.

I avoid them in my code.

[–] stifle867@programming.dev 2 points 11 months ago

You can usually restructure your code to avoid them and would suggest to do so where possible. In the same vein as GOTO being bad practice. It's simpler being able to follow a function's flow from top to bottom.