The text above describes "internal" linking, in which cmd/link parses and
links host object files (ELF, Mach-O, PE, and so on) into the final
executable itself. Keeping cmd/link simple means we cannot possibly
implement the full semantics of the host linker, so the kinds of
objects that can be linked directly into the binary is limited (other
code can only be used as a dynamic library). On the other hand, when

reported at `runtime._LostContendedRuntimeLock`. Complete stack traces of
runtime locks can be enabled with the [`runtimecontentionstacks`
setting](/pkg/runtime#hdr-Environment_Variable). These stack traces have
non-standard semantics, see setting documentation for details.

Go 1.22 added a new [`crypto/x509.Certificate`](/pkg/crypto/x509/#Certificate)
field, [`Policies`](/pkg/crypto/x509/#Certificate.Policies), which supports

pkg syscall (windows-386), const FILE_BEGIN ideal-int
pkg syscall (windows-386), const FILE_CURRENT ideal-int
pkg syscall (windows-386), const FILE_END ideal-int
pkg syscall (windows-386), const FILE_FLAG_BACKUP_SEMANTICS ideal-int
pkg syscall (windows-386), const FILE_FLAG_OVERLAPPED ideal-int
pkg syscall (windows-386), const FILE_LIST_DIRECTORY ideal-int
pkg syscall (windows-386), const FILE_MAP_COPY ideal-int

func fileEntryLess(x, y string) bool {
	xdir, xelem, _ := split(x)
	ydir, yelem, _ := split(y)
	return xdir < ydir || xdir == ydir && xelem < yelem
}

// Open opens the named file in the ZIP archive,
// using the semantics of fs.FS.Open:
// paths are always slash separated, with no
// leading / or ../ elements.
func (r *Reader) Open(name string) (fs.File, error) {
	r.initFileList()

	if !fs.ValidPath(name) {

pkg syscall (windows-386), const FILE_BEGIN = 0
pkg syscall (windows-386), const FILE_CURRENT = 1
pkg syscall (windows-386), const FILE_END = 2
pkg syscall (windows-386), const FILE_FLAG_BACKUP_SEMANTICS = 33554432
pkg syscall (windows-386), const FILE_FLAG_OVERLAPPED = 1073741824
pkg syscall (windows-386), const FILE_LIST_DIRECTORY = 1
pkg syscall (windows-386), const FILE_MAP_COPY = 1

</p>

<p>
Don't be clever.
</p>

<h3 id="overview">Informal Overview</h3>

<p>
Go approaches its memory model in much the same way as the rest of the language,
aiming to keep the semantics simple, understandable, and useful.
This section gives a general overview of the approach and should suffice for most programmers.
The memory model is specified more formally in the next section.
</p>

<p>

	// providing the ability to have sub-second resolution for timestamps.
	//
	// Some newer formats add their own extensions to PAX by defining their
	// own keys and assigning certain semantic meaning to the associated values.
	// For example, sparse file support in PAX is implemented using keys
	// defined by the GNU manual (e.g., "GNU.sparse.map").
	//
	// Reference:

<p><!-- CL 539016, https://go.dev/issue/63888: cmd/vet: do not report variable capture for loop variables with the new lifetime rules -->
  The behavior of the <code>vet</code> tool has changed to match
  the new semantics (see above) of loop variables in Go 1.22.
  When analyzing a file that requires Go 1.22 or newer
  (due to its go.mod file or a per-file build constraint),
  <code>vet</code>code> no longer reports references to