From 962830bfa92499e00a31572b0eeff9efdd68d374 Mon Sep 17 00:00:00 2001 From: Jason Alan Palmer Date: Mon, 14 Jan 2019 19:25:02 -0700 Subject: [PATCH] "named returns" -> "naked returns" --- CodeReviewComments.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/CodeReviewComments.md b/CodeReviewComments.md index 0686bcbf..ff9ac2cb 100644 --- a/CodeReviewComments.md +++ b/CodeReviewComments.md @@ -464,7 +464,7 @@ func (f *Foo) Location() (lat, long float64, err error) Naked returns are okay if the function is a handful of lines. Once it's a medium sized function, be explicit with your return values. Corollary: it's not worth it -to name result parameters just because it enables you to use named returns. +to name result parameters just because it enables you to use naked returns. Clarity of docs is always more important than saving a line or two in your function. Finally, in some cases you need to name a result parameter in order to change