src/cmd/go.mod. When a package outside std or cmd is imported
by a package inside std or cmd, the import path is interpreted
as if it had a "vendor/" prefix. For example, within "crypto/tls",
an import of "golang.org/x/crypto/cryptobyte" resolves to
"vendor/golang.org/x/crypto/cryptobyte". When a package with the
same path is imported from a package outside std or cmd, it will
be resolved normally. Consequently, a binary may be built with two

We only use our bug tracker for tracking bugs and tracking proposals going through the [Proposal Process](https://go.dev/s/proposal-process).

For asking questions, see:

* [The golang-nuts mailing list](https://groups.google.com/d/forum/golang-nuts)

* [The Go Forum](https://forum.golangbridge.org/), a web-based forum

* [Gophers Slack](https://gophers.slack.com), use the [invite app](https://invite.slack.golangbridge.org/) for access

pkg syscall (darwin-arm64), const EV_FLAG1 ideal-int
pkg syscall (darwin-arm64), const EV_ONESHOT = 16
pkg syscall (darwin-arm64), const EV_ONESHOT ideal-int
pkg syscall (darwin-arm64), const EV_OOBAND = 8192
pkg syscall (darwin-arm64), const EV_OOBAND ideal-int
pkg syscall (darwin-arm64), const EV_POLL = 4096
pkg syscall (darwin-arm64), const EV_POLL ideal-int
pkg syscall (darwin-arm64), const EV_RECEIPT = 64

list](https://groups.google.com/forum/#!forum/golang-nuts) or [other forums](https://golang.org/help/) first. If
the behavior you are seeing is confirmed as a bug or issue, it can easily be re-raised in the issue tracker.

## Filing issues

Sensitive security-related issues should be reported to [security@golang.org](mailto:security@golang.org).

# The environment overrides everything else.

# Use the Go module mirror and checksum database by default.
# See https://proxy.golang.org for details.
GOPROXY=https://proxy.golang.org,direct
GOSUMDB=sum.golang.org

# Automatically download newer toolchains as directed by go.mod files.
# See https://go.dev/doc/toolchain for details.

reliable, and efficient software.

![Gopher image](https://golang.org/doc/gopher/fiveyears.jpg)
*Gopher image by [Renee French][rf], licensed under [Creative Commons 4.0 Attributions license][cc4-by].*

Our canonical Git repository is located at https://go.googlesource.com/go.
There is a mirror of the repository at https://github.com/golang/go.

Unless otherwise noted, the Go source files are distributed under the

    > cd doc
    > rm -r next/*
    > cp -r initial/* next

Then edit `next/1-intro.md` to refer to the next version.

To prepare the release notes for a release, run `golang.org/x/build/cmd/relnote generate`.

pkg syscall (darwin-386), const EV_FLAG0 = 4096
pkg syscall (darwin-386), const EV_FLAG1 = 8192
pkg syscall (darwin-386), const EV_ONESHOT = 16
pkg syscall (darwin-386), const EV_OOBAND = 8192
pkg syscall (darwin-386), const EV_POLL = 4096
pkg syscall (darwin-386), const EV_RECEIPT = 64
pkg syscall (darwin-386), const EV_SYSFLAGS = 61440
pkg syscall (darwin-386), const EWOULDBLOCK = 35

Android
=======

For details on developing Go for Android, see the documentation in the
mobile subrepository:

	https://github.com/golang/mobile

To run the standard library tests, enable Cgo and use an appropriate
C compiler from the Android NDK. For example,

	CGO_ENABLED=1 \
	GOOS=android \
	GOARCH=arm64 \
	CC_FOR_TARGET=$NDK/toolchains/llvm/prebuilt/linux-x86_64/bin/aarch64-linux-android21-clang \
	./all.bash

`$GOROOT/bin/go` should install a symlink instead of relocating
or copying the `go` binary.

### Vet {#vet}

The `go vet` subcommand now includes the
[stdversion](https://beta.pkg.go.dev/golang.org/x/tools/go/analysis/passes/stdversion)
analyzer, which flags references to symbols that are too new for the version
of Go in effect in the referring file. (The effective version is determined