qbit/go
1
0
Fork 0
mirror of https://github.com/golang/go synced 2024-09-28 22:24:29 -06:00
Code Releases Activity

cmd/go/internal/help: update the documentation to match the design and implementation

Browse Source 
The existing documentation imply that the build constraints
should be ignored after a block comments, but actually it's not.

Fixes #63502

Change-Id: I0597934b7a7eeab8908bf06e1312169b3702bf05
Reviewed-on: https://go-review.googlesource.com/c/go/+/535635
Reviewed-by: Michael Matloob <matloob@golang.org>
LUCI-TryBot-Result: Go LUCI <golang-scoped@luci-project-accounts.iam.gserviceaccount.com>
Reviewed-by: Bryan Mills <bcmills@google.com>
Reviewed-by: Mark Pictor <mark.pictor@contrastsecurity.com>
Auto-Submit: Bryan Mills <bcmills@google.com>
Reviewed-by: Ian Lance Taylor <iant@google.com>
This commit is contained in:
Quan Tong 2023-10-16 15:39:48 +07:00 committed by Gopher Robot
parent 1e95fc7ffe
commit 214ce28503
2 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
src/cmd/go/alldocs.go
View File

@ -1926,7 +1926,7 @@
//
// Constraints may appear in any kind of source file (not just Go), but
// they must appear near the top of the file, preceded
// only by blank lines and other line comments. These rules mean that in Go
// only by blank lines and other comments. These rules mean that in Go
// files a build constraint must appear before the package clause.
//
// To distinguish build constraints from package documentation,

2
src/cmd/go/internal/help/helpdoc.go
View File

@ -829,7 +829,7 @@ line comment that begins
Constraints may appear in any kind of source file (not just Go), but
they must appear near the top of the file, preceded
only by blank lines and other line comments. These rules mean that in Go
only by blank lines and other comments. These rules mean that in Go
files a build constraint must appear before the package clause.
To distinguish build constraints from package documentation,