From 9cfd3e46f14fe5db36d6adf6af4caf789aa28d2e Mon Sep 17 00:00:00 2001 From: Brendan Tracey Date: Tue, 23 Jul 2019 10:12:18 +0100 Subject: [PATCH] stat/combin: Fix CombinationGenerator comment (#1028) It's confusing to say that Combination generates the next combination, when really it generates the current one with Next doing the advancing. --- stat/combin/combin.go | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/stat/combin/combin.go b/stat/combin/combin.go index 744911c9..c15540f6 100644 --- a/stat/combin/combin.go +++ b/stat/combin/combin.go @@ -119,7 +119,7 @@ func (c *CombinationGenerator) Next() bool { return true } -// Combination generates the next combination. If next is non-nil, it must have +// Combination generates the current combination. If next is non-nil, it must have // length k and the result will be stored in-place into combination. If combination // is nil a new slice will be allocated and returned. If all of the combinations // have already been constructed (Next() returns false), Combination will panic.