]> Cypherpunks repositories - gostls13.git/commitdiff
doc: avoid mentioning non-existence of u flag to fmt.Printf.
authorJim Kingdon <jim@bolt.me>
Thu, 8 Sep 2016 18:27:04 +0000 (11:27 -0700)
committerRob Pike <r@golang.org>
Fri, 9 Sep 2016 00:04:21 +0000 (00:04 +0000)
It is better to document what golang does, rather than how it differs
from languages which readers may or may not know.

That the output format is based on the type is basically self-evident
if you consider this just in go terms.

Change-Id: I0223e9b4cb67cc83a9ebe4d424e6c151d7ed600f
Reviewed-on: https://go-review.googlesource.com/28393
Reviewed-by: Rob Pike <r@golang.org>
src/fmt/doc.go

index c312914b44a48bf076934031318ea252f3cc7a9c..eb97e51d5d1cd090843df34a009e9c213b5e0588 100644 (file)
@@ -48,9 +48,6 @@
        Pointer:
                %p      base 16 notation, with leading 0x
 
-       There is no 'u' flag.  Integers are printed unsigned if they have unsigned type.
-       Similarly, there is no need to specify the size of the operand (int8, int64).
-
        The default format for %v is:
                bool:                    %t
                int, int8 etc.:          %d