- Sort Score
- Result 10 results
- Languages All
Results 1 - 3 of 3 for parseFileHeader (0.18 sec)
-
src/cmd/go/internal/imports/build.go
// Identify leading run of // comments and blank lines, // which must be followed by a blank line. // Also identify any //go:build comments. content, goBuild, _, err := parseFileHeader(content) if err != nil { return false } // If //go:build line is present, it controls. // Otherwise fall back to +build processing. var shouldBuild bool switch { case goBuild != nil:
Registered: Wed Jun 12 16:32:35 UTC 2024 - Last Modified: Thu Mar 30 18:50:57 UTC 2023 - 10.4K bytes - Viewed (0) -
src/cmd/go/internal/modindex/build.go
// Identify leading run of // comments and blank lines, // which must be followed by a blank line. // Also identify any //go:build comments. content, goBuildBytes, sawBinaryOnly, err := parseFileHeader(content) if err != nil { return "", nil, false, err } // If //go:build line is present, it controls, so no need to look for +build . // Otherwise, get plusBuild constraints. if goBuildBytes == nil {
Registered: Wed Jun 12 16:32:35 UTC 2024 - Last Modified: Fri Aug 25 17:39:23 UTC 2023 - 26.8K bytes - Viewed (0) -
src/go/build/build.go
} // parseFileHeader should be an internal detail, // but widely used packages access it using linkname. // Notable members of the hall of shame include: // - github.com/bazelbuild/bazel-gazelle // // Do not remove or change the type signature. // See go.dev/issue/67401. // //go:linkname parseFileHeader
Registered: Wed Jun 12 16:32:35 UTC 2024 - Last Modified: Wed May 29 16:25:21 UTC 2024 - 62.3K bytes - Viewed (0)