From 2a36f78e8795c939630e494319c5790bc519ba72 Mon Sep 17 00:00:00 2001 From: Jim Kingdon Date: Thu, 8 Sep 2016 11:27:04 -0700 Subject: [PATCH] doc: avoid mentioning non-existence of u flag to fmt.Printf. 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 --- src/fmt/doc.go | 3 --- 1 file changed, 3 deletions(-) diff --git a/src/fmt/doc.go b/src/fmt/doc.go index c312914b44..eb97e51d5d 100644 --- a/src/fmt/doc.go +++ b/src/fmt/doc.go @@ -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 -- 2.48.1