Lines Matching full:go

1 # Go support for Protocol Buffers - Google's data interchange format
7 Copyright 2010 The Go Authors.
10 This package and the code it generates requires at least Go 1.9.
12 This software implements Go bindings for protocol buffers.  For
21 - Of course, install the Go compiler and tools from
28   The simplest way is to run `go get -u github.com/golang/protobuf/protoc-gen-go`.
29   The compiler plugin, `protoc-gen-go`, will be installed in `$GOPATH/bin`
32 - If you need a particular version of `protoc-gen-go` (e.g., to match your
36   go get -d -u github.com/golang/protobuf/protoc-gen-go
37   git -C "$(go env GOPATH)"/src/github.com/golang/protobuf checkout $GIT_TAG
38   go install github.com/golang/protobuf/protoc-gen-go
42 generates Go source files that, once compiled, can access and manage
47 There is support for gRPC in Go using protocol buffers.
53 ## Using protocol buffers with Go ##
60 parameter set to the directory you want to output the Go code to.
64 The generated files will be suffixed .pb.go.  See the Test code below
70 correspond well to the Go notion of packages. In generated Go code,
71 each source `.proto` file is associated with a single Go package. The
82 generated `.pb.go` files, but any number of `.pb.go` files may be
83 contained in the same Go package.
86 `.proto` suffix with `.pb.go` (e.g., `foo.proto` produces `foo.pb.go`).
96   # writes ./github.com/golang/protobuf/p/x.pb.go
105 # generate ./inputs/x.pb.go
111 the interface provided in Go for protocol buffers. Here is an edited
116 Go source code generated for .proto files by the protocol compiler.
177 ```go
223   associated with Go package quux/shme.  This is subject to the
236 If a proto file specifies RPC services, protoc-gen-go can be instructed to
238 the `plugins` parameter to protoc-gen-go; the usual way is to insert it into
276 You should, whenever possible, use generated code created by the `protoc-gen-go`
287 The `protoc-gen-go/generator` package exposes a plugin interface,