encoding/binary: Varint signature/docs could benefit from name result parameters

[bradfitz]

https://pkg.go.dev/encoding/binary@master#Varint says:

func Varint(buf []byte) (int64, int)

Varint decodes an int64 from buf and returns that value and the number of bytes read (> 0). If an error occurred, the value is 0 and the number of bytes n is <= 0 with the following meaning:

n == 0: buf too small
n  < 0: value larger than 64 bits (overflow)
        and -n is the number of bytes read

--

That signature and docs (referencing n that's never named) are really asking to have named results.

[Shisthruna28]

@ianlancetaylor I would like to contribute to this, can you explain what changes need to be done?

[seankhliao]

@Shisthruna28 adjust the function signature to name the results in a way that matches the documentation
our contributing process can be found here: https://golang.org/doc/contribute

[gopherbot]

Change https://golang.org/cl/364277 mentions this issue: docs: improved function signature with named result